Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9384bb3b03fa5e3f39504dcd21b45f71561bd316b82c433a39359e063b01319

Tx prefix hash: a44c5da95ce739c828b030fb8dc8a03dbe8005c39326839f6b5250cbf486b117
Tx public key: 35d1efd4d2545f8838475dc8d34a93bb53c6920632e599768a9f3a495e5f3a1b
Timestamp: 1720439737 Timestamp [UCT]: 2024-07-08 11:55:37 Age [y:d:h:m:s]: 00:317:14:16:36
Block: 1061210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226962 RingCT/type: yes/0
Extra: 0135d1efd4d2545f8838475dc8d34a93bb53c6920632e599768a9f3a495e5f3a1b02110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9771741b43bc32491800419ff3ad3b041dee25dd4a7cecb65f1f92bae11e538 0.600000000000 1531701 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": 1061220, "vin": [ { "gen": { "height": 1061210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9771741b43bc32491800419ff3ad3b041dee25dd4a7cecb65f1f92bae11e538" } } ], "extra": [ 1, 53, 209, 239, 212, 210, 84, 95, 136, 56, 71, 93, 200, 211, 74, 147, 187, 83, 198, 146, 6, 50, 229, 153, 118, 138, 159, 58, 73, 94, 95, 58, 27, 2, 17, 0, 0, 0, 12, 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