Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 404d8aca4282818a020bbd837ee82a4b5e118b2e0ff94efb971bbca1281134a0

Tx prefix hash: beaa3e4eb90d57729e9799e600bc81a0b16276d11b4ca9fcdf61a981279791c4
Tx public key: 704404cbf31b2b54c0f98712cd275bd8d1e1c430b8fd5c52f684c488bd6e69e5
Timestamp: 1733729682 Timestamp [UCT]: 2024-12-09 07:34:42 Age [y:d:h:m:s]: 00:350:13:43:38
Block: 1171285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248085 RingCT/type: yes/0
Extra: 01704404cbf31b2b54c0f98712cd275bd8d1e1c430b8fd5c52f684c488bd6e69e5021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed1636c452f744712f99bde856d8379ff60648547fdca57fd2b218be247011ea 0.600000000000 1657024 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": 1171295, "vin": [ { "gen": { "height": 1171285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed1636c452f744712f99bde856d8379ff60648547fdca57fd2b218be247011ea" } } ], "extra": [ 1, 112, 68, 4, 203, 243, 27, 43, 84, 192, 249, 135, 18, 205, 39, 91, 216, 209, 225, 196, 48, 184, 253, 92, 82, 246, 132, 196, 136, 189, 110, 105, 229, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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