Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a7cd53be30ceae2f71f9efcf18ed7e89bb0c20899bd410df919590f8df2988b

Tx prefix hash: 2ec85db8f6c6c86b68c46f8c9cbee29d56db63d2738ff17c2d0ab056c222c046
Tx public key: a32b4ee991b87a73d91f89c9da9ba17611b88c8d9e7cd06c07abf104008bca80
Timestamp: 1716766252 Timestamp [UCT]: 2024-05-26 23:30:52 Age [y:d:h:m:s]: 00:297:19:32:48
Block: 1030752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212858 RingCT/type: yes/0
Extra: 01a32b4ee991b87a73d91f89c9da9ba17611b88c8d9e7cd06c07abf104008bca800211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb05a4e7a2c3e363dcfc6411206af1b7ace7a5dfee0b2b0aeeb0192194c77e0e 0.600000000000 1499033 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": 1030762, "vin": [ { "gen": { "height": 1030752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb05a4e7a2c3e363dcfc6411206af1b7ace7a5dfee0b2b0aeeb0192194c77e0e" } } ], "extra": [ 1, 163, 43, 78, 233, 145, 184, 122, 115, 217, 31, 137, 201, 218, 155, 161, 118, 17, 184, 140, 141, 158, 124, 208, 108, 7, 171, 241, 4, 0, 139, 202, 128, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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