Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1be6d2b51031581c2c012e60aee2f0bc88d374f304bb484eb1ac93ef0a5d1ee5

Tx prefix hash: 878ac79f989857d62315a1199ae4211e690be303c1f53159051a5cd08de042aa
Tx public key: 7acbcb77db318c6ca454f5d5ac7ac58fc7947c519ea211cc8aff0844fec2e8e4
Timestamp: 1717856815 Timestamp [UCT]: 2024-06-08 14:26:55 Age [y:d:h:m:s]: 00:335:01:09:30
Block: 1039791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239455 RingCT/type: yes/0
Extra: 017acbcb77db318c6ca454f5d5ac7ac58fc7947c519ea211cc8aff0844fec2e8e4021100000003d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04e824490c2aeea2a2bddea86ced9966ba9a49d92eab5171369b614d70256516 0.600000000000 1508446 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": 1039801, "vin": [ { "gen": { "height": 1039791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04e824490c2aeea2a2bddea86ced9966ba9a49d92eab5171369b614d70256516" } } ], "extra": [ 1, 122, 203, 203, 119, 219, 49, 140, 108, 164, 84, 245, 213, 172, 122, 197, 143, 199, 148, 124, 81, 158, 162, 17, 204, 138, 255, 8, 68, 254, 194, 232, 228, 2, 17, 0, 0, 0, 3, 215, 73, 245, 17, 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