Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 130c665aa83712a0f06aaf164cfea0c7b5df83d6a46570d2b54c963a69050fdc

Tx prefix hash: a1a61009707634bb500292cedf8d565e6ebe8c09f011695408ad1b07b45c6817
Tx public key: 26364ff28761e4e30c0b58ae809830dfac08b3ada8c0a61a6dc6491cfd1a7bae
Timestamp: 1699326902 Timestamp [UCT]: 2023-11-07 03:15:02 Age [y:d:h:m:s]: 01:362:23:05:34
Block: 886163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518316 RingCT/type: yes/0
Extra: 0126364ff28761e4e30c0b58ae809830dfac08b3ada8c0a61a6dc6491cfd1a7bae021100000001679a8a81000000000000000000

1 output(s) for total of 0.710843703000 dcy

stealth address amount amount idx
00: 931b5223e5b70744b72237ea6ecb13558e333106921151887dcd854680e4eebe 0.710843703000 1341972 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": 886173, "vin": [ { "gen": { "height": 886163 } } ], "vout": [ { "amount": 710843703, "target": { "key": "931b5223e5b70744b72237ea6ecb13558e333106921151887dcd854680e4eebe" } } ], "extra": [ 1, 38, 54, 79, 242, 135, 97, 228, 227, 12, 11, 88, 174, 128, 152, 48, 223, 172, 8, 179, 173, 168, 192, 166, 26, 109, 198, 73, 28, 253, 26, 123, 174, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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