Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 378b9574464117c56daf213e0f34e2e0ccf92fb8c3a48647d2b267d659adfc01

Tx prefix hash: bf3765cd8767c1cdea58cecbd2bf7ad06ae3680e55711d54b2a5970b841b4a21
Tx public key: e08eb0ba761dc0e1717d4ec55fae9db7eac8a3c5869a8f149a6c2894e16e8851
Timestamp: 1646773945 Timestamp [UCT]: 2022-03-08 21:12:25 Age [y:d:h:m:s]: 03:065:12:23:22
Block: 454235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 826981 RingCT/type: yes/0
Extra: 01e08eb0ba761dc0e1717d4ec55fae9db7eac8a3c5869a8f149a6c2894e16e8851021100000003bf7ee4e7000000000000000000

1 output(s) for total of 19.183646174000 dcy

stealth address amount amount idx
00: 23f1ce84d8897460e0f84c3875e5148d4883b4f4226091e802033d41005c516d 19.183646174000 869842 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": 454245, "vin": [ { "gen": { "height": 454235 } } ], "vout": [ { "amount": 19183646174, "target": { "key": "23f1ce84d8897460e0f84c3875e5148d4883b4f4226091e802033d41005c516d" } } ], "extra": [ 1, 224, 142, 176, 186, 118, 29, 192, 225, 113, 125, 78, 197, 95, 174, 157, 183, 234, 200, 163, 197, 134, 154, 143, 20, 154, 108, 40, 148, 225, 110, 136, 81, 2, 17, 0, 0, 0, 3, 191, 126, 228, 231, 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