Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f13abc0ddd38dd87f0f5cb199962d926191f6f866e8ccc1b35754b9501e4c8c4

Tx prefix hash: a13beb3825f6be41e9e12436d103a88a69dac2fc95685aea0845c7606fd37663
Tx public key: 9e4997c99da11824c60d8fa02577358799c4bd405d0cef184e5106f735f4f068
Timestamp: 1723810155 Timestamp [UCT]: 2024-08-16 12:09:15 Age [y:d:h:m:s]: 01:088:00:27:04
Block: 1089145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321375 RingCT/type: yes/0
Extra: 019e4997c99da11824c60d8fa02577358799c4bd405d0cef184e5106f735f4f06802110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 442df85073f4573bf9fea55cffb6f3dd598ce60fd1bf5c6fd0a30b2c8602fcac 0.600000000000 1563764 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": 1089155, "vin": [ { "gen": { "height": 1089145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "442df85073f4573bf9fea55cffb6f3dd598ce60fd1bf5c6fd0a30b2c8602fcac" } } ], "extra": [ 1, 158, 73, 151, 201, 157, 161, 24, 36, 198, 13, 143, 160, 37, 119, 53, 135, 153, 196, 189, 64, 93, 12, 239, 24, 78, 81, 6, 247, 53, 244, 240, 104, 2, 17, 0, 0, 0, 6, 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