Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e4370a1fff660a4529754683df040bad486941f20a366cd165b8116662a2f5c

Tx prefix hash: 8de7ee7f23d2a2843fc4fad3570383faa3acb44d1fc07e3cc041e611ed07a97d
Tx public key: 5fa4965304149526cb7be4e397ce8d86cb9d8416bb39b1d0a7ac0f1da54e4768
Timestamp: 1727144612 Timestamp [UCT]: 2024-09-24 02:23:32 Age [y:d:h:m:s]: 00:171:04:30:25
Block: 1116790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122159 RingCT/type: yes/0
Extra: 015fa4965304149526cb7be4e397ce8d86cb9d8416bb39b1d0a7ac0f1da54e476802110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 369b7c09a5fe932caddebbd88fcd23e7ba628f56b515c4e65efb96d2ee0752de 0.600000000000 1597397 of 15

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": 1116800, "vin": [ { "gen": { "height": 1116790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "369b7c09a5fe932caddebbd88fcd23e7ba628f56b515c4e65efb96d2ee0752de" } } ], "extra": [ 1, 95, 164, 150, 83, 4, 20, 149, 38, 203, 123, 228, 227, 151, 206, 141, 134, 203, 157, 132, 22, 187, 57, 177, 208, 167, 172, 15, 29, 165, 78, 71, 104, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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