Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4cae898255a2710f6e3ea0aeb3e1b52df6dd23e694cb7f6fa41ab926b7bf519

Tx prefix hash: 967d8a1bb2d848ab169974ec2d927634eab5d49b4fc61130bfd9e28ef4585ce6
Tx public key: afc1f509560c31c7f8bf5de7cac5178798be2ee8b8963efdd48cfbdde76b36de
Timestamp: 1716423743 Timestamp [UCT]: 2024-05-23 00:22:23 Age [y:d:h:m:s]: 01:252:05:55:39
Block: 1027907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438812 RingCT/type: yes/0
Extra: 01afc1f509560c31c7f8bf5de7cac5178798be2ee8b8963efdd48cfbdde76b36de02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5632f7c6574f512e1860003eb2c26ff9abe36fd11d701c82d3407f2caa61dca 0.600000000000 1495782 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": 1027917, "vin": [ { "gen": { "height": 1027907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5632f7c6574f512e1860003eb2c26ff9abe36fd11d701c82d3407f2caa61dca" } } ], "extra": [ 1, 175, 193, 245, 9, 86, 12, 49, 199, 248, 191, 93, 231, 202, 197, 23, 135, 152, 190, 46, 232, 184, 150, 62, 253, 212, 140, 251, 221, 231, 107, 54, 222, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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