Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09fea55317624db99f96efe4eadba3b2f9ed9f72ee4ca0b268ef9637937c4585

Tx prefix hash: 0ccfbd030e192e5e77b2bd6aaa354222969b7d1a857033b2f89d387cc274b252
Tx public key: 8c4d218e25bb59415a8b0a1f63924e852e3c34561fa579e0f6239d38158cb77a
Timestamp: 1721954414 Timestamp [UCT]: 2024-07-26 00:40:14 Age [y:d:h:m:s]: 00:273:00:46:08
Block: 1073752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195065 RingCT/type: yes/0
Extra: 018c4d218e25bb59415a8b0a1f63924e852e3c34561fa579e0f6239d38158cb77a02110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae2caa205cf8a6a887291e33decc4d1de7b55551b08eb85b7d5bcac90f66ae37 0.600000000000 1546259 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": 1073762, "vin": [ { "gen": { "height": 1073752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae2caa205cf8a6a887291e33decc4d1de7b55551b08eb85b7d5bcac90f66ae37" } } ], "extra": [ 1, 140, 77, 33, 142, 37, 187, 89, 65, 90, 139, 10, 31, 99, 146, 78, 133, 46, 60, 52, 86, 31, 165, 121, 224, 246, 35, 157, 56, 21, 140, 183, 122, 2, 17, 0, 0, 0, 15, 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