Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee449f180fb83df47837d899dc6c63c7ada23b34dc2d5ca9bbd04a41bd80e44e

Tx prefix hash: a405f8da7a23c516fc296aeb13bc7dfc7f62929d88e23a4014a052a94db629e9
Tx public key: 19e8450a8cd0d4f7eb73bc91920f4bde1c70d7fbe392f17f204e14b228d0c489
Timestamp: 1704362093 Timestamp [UCT]: 2024-01-04 09:54:53 Age [y:d:h:m:s]: 01:093:07:00:29
Block: 927918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327757 RingCT/type: yes/0
Extra: 0119e8450a8cd0d4f7eb73bc91920f4bde1c70d7fbe392f17f204e14b228d0c489021100000002c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4163454beff8ceb3abeb466ff468eff46bf8b696245dc3a80e9fbec03e0c5e4d 0.600000000000 1385760 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": 927928, "vin": [ { "gen": { "height": 927918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4163454beff8ceb3abeb466ff468eff46bf8b696245dc3a80e9fbec03e0c5e4d" } } ], "extra": [ 1, 25, 232, 69, 10, 140, 208, 212, 247, 235, 115, 188, 145, 146, 15, 75, 222, 28, 112, 215, 251, 227, 146, 241, 127, 32, 78, 20, 178, 40, 208, 196, 137, 2, 17, 0, 0, 0, 2, 197, 69, 41, 96, 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