Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2dd0697d951167242c845a4bdca22e3d9166f705e404a0519796dfefc6bd807

Tx prefix hash: ee51a0f9478cdef546061ffac9e6c87179a0e8d9ddd178bd8bf3daa932d95b66
Tx public key: f9f9e3b43f843e83973d043929e32d54afc427687fe3b39b191f516852f5cfb7
Timestamp: 1731637572 Timestamp [UCT]: 2024-11-15 02:26:12 Age [y:d:h:m:s]: 00:165:18:16:20
Block: 1153932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118329 RingCT/type: yes/0
Extra: 01f9f9e3b43f843e83973d043929e32d54afc427687fe3b39b191f516852f5cfb70211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1897ff335c1e0fe4ba1a612aee70944a30ace68dcadecc499ba313bbffa8bb2 0.600000000000 1639543 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": 1153942, "vin": [ { "gen": { "height": 1153932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1897ff335c1e0fe4ba1a612aee70944a30ace68dcadecc499ba313bbffa8bb2" } } ], "extra": [ 1, 249, 249, 227, 180, 63, 132, 62, 131, 151, 61, 4, 57, 41, 227, 45, 84, 175, 196, 39, 104, 127, 227, 179, 155, 25, 31, 81, 104, 82, 245, 207, 183, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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