Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1558c9179d98f3f0d0fb2ff0e8a8f2a016c1f41fec9e01621c01491bf16fc9ca

Tx prefix hash: 8e3a2ccba72e148e083f7863c94444c9cbc8d50dcbad4224ed1eef84c15c84c0
Tx public key: ed0ec6be3e103584737bbff71eeaf3d4ec11aea3f3e0b932243445a15602e866
Timestamp: 1721437839 Timestamp [UCT]: 2024-07-20 01:10:39 Age [y:d:h:m:s]: 00:096:03:16:50
Block: 1069514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68793 RingCT/type: yes/0
Extra: 01ed0ec6be3e103584737bbff71eeaf3d4ec11aea3f3e0b932243445a15602e866021100000004162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33d91430a1f1bee82022b98fec7fac1eefe2d840c3b5d9fa452e5f554cbca837 0.600000000000 1540959 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": 1069524, "vin": [ { "gen": { "height": 1069514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33d91430a1f1bee82022b98fec7fac1eefe2d840c3b5d9fa452e5f554cbca837" } } ], "extra": [ 1, 237, 14, 198, 190, 62, 16, 53, 132, 115, 123, 191, 247, 30, 234, 243, 212, 236, 17, 174, 163, 243, 224, 185, 50, 36, 52, 69, 161, 86, 2, 232, 102, 2, 17, 0, 0, 0, 4, 22, 38, 19, 170, 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