Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 3bb070436b0c54df58ed89fb902a62b2a32261c3294e350a2883d0303088026d

Tx prefix hash: 99ce7a857cc8a3e13ae7860fb7c0918096b92122533c47f15dd4c24f3a9468a7
Tx public key: 7a7d10f5a7d0b239e5df588decf9d5ad199134d1e0346268bd767cad880bc57c
Timestamp: 1673164014 Timestamp [UCT]: 2023-01-08 07:46:54 Age [y:d:h:m:s]: 02:140:14:14:53
Block: 670112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 622215 RingCT/type: yes/0
Extra: 017a7d10f5a7d0b239e5df588decf9d5ad199134d1e0346268bd767cad880bc57c02110000000352542ceb000000000000000000

1 output(s) for total of 3.695223612000 dcy

stealth address amount amount idx
00: 3c80dfb8c1c77fe76905d230eca1b6b614768de8332b5a97eeb9364eb05370a3 3.695223612000 1111485 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 670122, "vin": [ { "gen": { "height": 670112 } } ], "vout": [ { "amount": 3695223612, "target": { "key": "3c80dfb8c1c77fe76905d230eca1b6b614768de8332b5a97eeb9364eb05370a3" } } ], "extra": [ 1, 122, 125, 16, 245, 167, 208, 178, 57, 229, 223, 88, 141, 236, 249, 213, 173, 25, 145, 52, 209, 224, 52, 98, 104, 189, 118, 124, 173, 136, 11, 197, 124, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8