Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 668534ec0ecd60ca0a79bb735abe547805e70e3dfad13159b0c98d33d4981cf8

Tx prefix hash: 1c7c5c859f2c1d8ae3f66dbe524f59141754586aec4357d8bfae3b47f04ef37e
Tx public key: c61558f7886a85af5ef40717436945fd609fb9c5d6c5b2990451a49de798057f
Timestamp: 1729457256 Timestamp [UCT]: 2024-10-20 20:47:36 Age [y:d:h:m:s]: 00:081:00:28:00
Block: 1135943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57913 RingCT/type: yes/0
Extra: 01c61558f7886a85af5ef40717436945fd609fb9c5d6c5b2990451a49de798057f0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3a5d52fc943ee9d951766a109d4e1f5730e20ed8cbfa754cefd2db9e06dcc91 0.600000000000 1619284 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": 1135953, "vin": [ { "gen": { "height": 1135943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3a5d52fc943ee9d951766a109d4e1f5730e20ed8cbfa754cefd2db9e06dcc91" } } ], "extra": [ 1, 198, 21, 88, 247, 136, 106, 133, 175, 94, 244, 7, 23, 67, 105, 69, 253, 96, 159, 185, 197, 214, 197, 178, 153, 4, 81, 164, 157, 231, 152, 5, 127, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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