Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d57a365454d9531a1945956f9ec7dae3c2fa45432c84dae76c702218131484f

Tx prefix hash: a6f575f702138ef3fd349a672c67fe540d422b3154c40f546c77140bba76006e
Tx public key: 2ce9daa616a1a8602f3d6b5ab2e2570eac69ae152d62437814b2d8f969c5b48d
Timestamp: 1723548635 Timestamp [UCT]: 2024-08-13 11:30:35 Age [y:d:h:m:s]: 00:260:00:29:07
Block: 1086973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185745 RingCT/type: yes/0
Extra: 012ce9daa616a1a8602f3d6b5ab2e2570eac69ae152d62437814b2d8f969c5b48d02110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f0d9882af9a5f87415c17dd8e12f26ceff7fb5442dd84344fe79b1c1230ec85 0.600000000000 1561572 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": 1086983, "vin": [ { "gen": { "height": 1086973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f0d9882af9a5f87415c17dd8e12f26ceff7fb5442dd84344fe79b1c1230ec85" } } ], "extra": [ 1, 44, 233, 218, 166, 22, 161, 168, 96, 47, 61, 107, 90, 178, 226, 87, 14, 172, 105, 174, 21, 45, 98, 67, 120, 20, 178, 216, 249, 105, 197, 180, 141, 2, 17, 0, 0, 0, 14, 145, 225, 60, 4, 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