Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b85891e70668e7eee1ba5428fb34fa345a94178bd27913a9ffc58cb6e32cb59

Tx prefix hash: a091f575ecdfd7162e0b1a9c2b22122cb79d443fc3705d924f0210960d674187
Tx public key: 17f68866034583397f70944d025788a86d5df24f15c99aa43cda1b4d3c85399f
Timestamp: 1732988941 Timestamp [UCT]: 2024-11-30 17:49:01 Age [y:d:h:m:s]: 00:343:06:50:37
Block: 1165138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242869 RingCT/type: yes/0
Extra: 0117f68866034583397f70944d025788a86d5df24f15c99aa43cda1b4d3c85399f021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b713d165477632263b52619ae2b15d3ff45aea5b16ffcf0fe1b2ab5c5a2fa853 0.600000000000 1650813 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": 1165148, "vin": [ { "gen": { "height": 1165138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b713d165477632263b52619ae2b15d3ff45aea5b16ffcf0fe1b2ab5c5a2fa853" } } ], "extra": [ 1, 23, 246, 136, 102, 3, 69, 131, 57, 127, 112, 148, 77, 2, 87, 136, 168, 109, 93, 242, 79, 21, 201, 154, 164, 60, 218, 27, 77, 60, 133, 57, 159, 2, 17, 0, 0, 0, 7, 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