Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efa76e4d053108a399f519cdb55db092477010d5c9b36200ebd380799cfdb1a1

Tx prefix hash: b4d84a89ecf1ce7d1af1083f67e2bb03bc5ca9aedf4edb3a993cd3f5f7057986
Tx public key: 1b14663fe876a82207f9dda2bf09f57e1e13332d990a37fa53cb842d4fc1d882
Timestamp: 1730518601 Timestamp [UCT]: 2024-11-02 03:36:41 Age [y:d:h:m:s]: 00:135:08:33:36
Block: 1144676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96588 RingCT/type: yes/0
Extra: 011b14663fe876a82207f9dda2bf09f57e1e13332d990a37fa53cb842d4fc1d8820211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00cf402687e46a9a4e2144142b0f8aaef49b64663443e9b7e4afd11e7687dbac 0.600000000000 1628955 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": 1144686, "vin": [ { "gen": { "height": 1144676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00cf402687e46a9a4e2144142b0f8aaef49b64663443e9b7e4afd11e7687dbac" } } ], "extra": [ 1, 27, 20, 102, 63, 232, 118, 168, 34, 7, 249, 221, 162, 191, 9, 245, 126, 30, 19, 51, 45, 153, 10, 55, 250, 83, 203, 132, 45, 79, 193, 216, 130, 2, 17, 0, 0, 0, 1, 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