Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d0ef2758353985b510266193695f76399e5d8e3b1bb892a2633d9257739db59

Tx prefix hash: a9971f53a2cc05434c745af65d6fc6558ea35c6b548ccc0e01a053b219a092ae
Tx public key: 88916cbc0daf7cb93e8cf68b2f61562a10f6349fbaace70dc771adf50995a996
Timestamp: 1705053874 Timestamp [UCT]: 2024-01-12 10:04:34 Age [y:d:h:m:s]: 01:067:20:45:59
Block: 933635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309610 RingCT/type: yes/0
Extra: 0188916cbc0daf7cb93e8cf68b2f61562a10f6349fbaace70dc771adf50995a9960211000000150011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cb0eb6e57e243d35ca67153eb3be2f063ff69fd92ba2b6b7271c1a6d8a9174e 0.600000000000 1391605 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": 933645, "vin": [ { "gen": { "height": 933635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cb0eb6e57e243d35ca67153eb3be2f063ff69fd92ba2b6b7271c1a6d8a9174e" } } ], "extra": [ 1, 136, 145, 108, 188, 13, 175, 124, 185, 62, 140, 246, 139, 47, 97, 86, 42, 16, 246, 52, 159, 186, 172, 231, 13, 199, 113, 173, 245, 9, 149, 169, 150, 2, 17, 0, 0, 0, 21, 0, 17, 5, 91, 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