Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb7bac1b90d2e8e6193a357e18e4f32aa1c9f523ad71802e623a79313fb8b8fc

Tx prefix hash: cf7cf0095c98a3836f099a337ff0a380d2b96f33c35643b817ca32657793edde
Tx public key: 13402e2ba122439cd47da33e762b731b1710c67b8f6ac14ae8064b7a25d0e9b2
Timestamp: 1710427087 Timestamp [UCT]: 2024-03-14 14:38:07 Age [y:d:h:m:s]: 01:062:20:15:59
Block: 978215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305899 RingCT/type: yes/0
Extra: 0113402e2ba122439cd47da33e762b731b1710c67b8f6ac14ae8064b7a25d0e9b202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b9f79e53d28b142db3b8c8fbf11741bd4b250c3049bc2e7124923ff97af4432 0.600000000000 1438236 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": 978225, "vin": [ { "gen": { "height": 978215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b9f79e53d28b142db3b8c8fbf11741bd4b250c3049bc2e7124923ff97af4432" } } ], "extra": [ 1, 19, 64, 46, 43, 161, 34, 67, 156, 212, 125, 163, 62, 118, 43, 115, 27, 23, 16, 198, 123, 143, 106, 193, 74, 232, 6, 75, 122, 37, 208, 233, 178, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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