Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 538dbf9a4d146839855435edd61a0a0b038160930a3ad65994f166ab29f18141

Tx prefix hash: ba8855d55fc5f0c05fa44ec9c575f79a75bc8f4056b6f7d251430bc85fed9fff
Tx public key: 3b08c40a0a540f3fb922a492378126926b7920ae97a56b319ae66f3cee73cb54
Timestamp: 1725527341 Timestamp [UCT]: 2024-09-05 09:09:01 Age [y:d:h:m:s]: 00:283:13:20:38
Block: 1103380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202451 RingCT/type: yes/0
Extra: 013b08c40a0a540f3fb922a492378126926b7920ae97a56b319ae66f3cee73cb5402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc57c08fb5eaffc4eb2e82483362cfa1fd7047fcfb66709742e44de62e7ef543 0.600000000000 1580187 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": 1103390, "vin": [ { "gen": { "height": 1103380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc57c08fb5eaffc4eb2e82483362cfa1fd7047fcfb66709742e44de62e7ef543" } } ], "extra": [ 1, 59, 8, 196, 10, 10, 84, 15, 63, 185, 34, 164, 146, 55, 129, 38, 146, 107, 121, 32, 174, 151, 165, 107, 49, 154, 230, 111, 60, 238, 115, 203, 84, 2, 17, 0, 0, 0, 3, 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