Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d492a2199a6409e0f0ad0a0aa68c2ecffc6a0d2aca96ace232a8eb4de206b6a

Tx prefix hash: 2a332bd9a90a493d2f3d4be76bdba25f4c1d8ad0f1e891f1520aa2914457cda8
Tx public key: 9ebd7e77ee9be67be5a63cbba006d4256868efb1202c2fddd3f5dfc1cf9c143a
Timestamp: 1726483123 Timestamp [UCT]: 2024-09-16 10:38:43 Age [y:d:h:m:s]: 00:181:16:24:29
Block: 1111298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129681 RingCT/type: yes/0
Extra: 019ebd7e77ee9be67be5a63cbba006d4256868efb1202c2fddd3f5dfc1cf9c143a021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5eb301afe7b4a74dd8dc8252d22e4f60feeabd72e7d89dcfeb8c7079a31a7bf7 0.600000000000 1590209 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": 1111308, "vin": [ { "gen": { "height": 1111298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5eb301afe7b4a74dd8dc8252d22e4f60feeabd72e7d89dcfeb8c7079a31a7bf7" } } ], "extra": [ 1, 158, 189, 126, 119, 238, 155, 230, 123, 229, 166, 60, 187, 160, 6, 212, 37, 104, 104, 239, 177, 32, 44, 47, 221, 211, 245, 223, 193, 207, 156, 20, 58, 2, 17, 0, 0, 0, 7, 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