Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ab4325b18a9a8a4392f32cbf378de6905d265cad37c059e85a25468f17d13ba

Tx prefix hash: 0abf23b8c51c6a1e649e83f25a20d4ec06eafd9aad9f3b7a9f5f3f024127a06e
Tx public key: 9d1e15bd56c26acf99acd6be82dabdcca97c3a4cc6f73193742866f24c892710
Timestamp: 1699531224 Timestamp [UCT]: 2023-11-09 12:00:24 Age [y:d:h:m:s]: 01:131:10:05:27
Block: 887869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355126 RingCT/type: yes/0
Extra: 019d1e15bd56c26acf99acd6be82dabdcca97c3a4cc6f73193742866f24c892710021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.701651458000 dcy

stealth address amount amount idx
00: e4c37bfd0692d63345e1b5bd99025a2930279c589eb19e9e48fedbae01848ed3 0.701651458000 1343776 of 0

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": 887879, "vin": [ { "gen": { "height": 887869 } } ], "vout": [ { "amount": 701651458, "target": { "key": "e4c37bfd0692d63345e1b5bd99025a2930279c589eb19e9e48fedbae01848ed3" } } ], "extra": [ 1, 157, 30, 21, 189, 86, 194, 106, 207, 153, 172, 214, 190, 130, 218, 189, 204, 169, 124, 58, 76, 198, 247, 49, 147, 116, 40, 102, 242, 76, 137, 39, 16, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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