Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d0d50583c3b489d39c000a7721cabc14590159406336342d56d3ae04bdc6a0f

Tx prefix hash: 68ef90ddbbe5a4014e5c5e28a2d8cd89f93981393fd77d5d85741e0d4bac12b3
Tx public key: 4bc7c544b5025d8a6187bbf6f668ea57a427729dc9c131930d453d1941a03fe6
Timestamp: 1722091411 Timestamp [UCT]: 2024-07-27 14:43:31 Age [y:d:h:m:s]: 00:088:06:05:33
Block: 1074894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63190 RingCT/type: yes/0
Extra: 014bc7c544b5025d8a6187bbf6f668ea57a427729dc9c131930d453d1941a03fe6021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dc6d63e3d0988bfc8c5337b3430548b946f4206a1f5d9308342a4e42eab6cd5 0.600000000000 1547413 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": 1074904, "vin": [ { "gen": { "height": 1074894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dc6d63e3d0988bfc8c5337b3430548b946f4206a1f5d9308342a4e42eab6cd5" } } ], "extra": [ 1, 75, 199, 197, 68, 181, 2, 93, 138, 97, 135, 187, 246, 246, 104, 234, 87, 164, 39, 114, 157, 201, 193, 49, 147, 13, 69, 61, 25, 65, 160, 63, 230, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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