Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 958269544410afa43bcb6237e755c145fa0c344fbfcd3592e389100ac01412e3

Tx prefix hash: 2835d93e03eb853dd7799a5d86af96943b98830dba998e455d1ee9ddb36aa688
Tx public key: 0747b3f9061cf47b2dd10dfa1eeb8774a7520b0e087226d69d7b4c0c5e1aeeb5
Timestamp: 1709464580 Timestamp [UCT]: 2024-03-03 11:16:20 Age [y:d:h:m:s]: 01:061:19:11:10
Block: 970218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305186 RingCT/type: yes/0
Extra: 010747b3f9061cf47b2dd10dfa1eeb8774a7520b0e087226d69d7b4c0c5e1aeeb502110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0640f2a6be1e2592f1ad48fbf799140430fd67e6fa8389e5c9f1b21de37ad1b 0.600000000000 1430069 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": 970228, "vin": [ { "gen": { "height": 970218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0640f2a6be1e2592f1ad48fbf799140430fd67e6fa8389e5c9f1b21de37ad1b" } } ], "extra": [ 1, 7, 71, 179, 249, 6, 28, 244, 123, 45, 209, 13, 250, 30, 235, 135, 116, 167, 82, 11, 14, 8, 114, 38, 214, 157, 123, 76, 12, 94, 26, 238, 181, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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