Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e447e949c0c5af1adcd678c97fa9701e93f15b6c56566e6b5c595bf616c5213f

Tx prefix hash: 6e2b1ca09998847ac67bf5f6b2db2b283f8a56f7ae8e98909f1760950c61e0f0
Tx public key: 8173a9af73a09784cef9ffa774f95cde93271f6e1f141e9253fed9756e8dc1d4
Timestamp: 1724894092 Timestamp [UCT]: 2024-08-29 01:14:52 Age [y:d:h:m:s]: 00:269:02:29:01
Block: 1098126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192228 RingCT/type: yes/0
Extra: 018173a9af73a09784cef9ffa774f95cde93271f6e1f141e9253fed9756e8dc1d402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 905ca857f4be9893df8cc4976489b933778dea8d09455c3475739481be6e45e0 0.600000000000 1573737 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": 1098136, "vin": [ { "gen": { "height": 1098126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "905ca857f4be9893df8cc4976489b933778dea8d09455c3475739481be6e45e0" } } ], "extra": [ 1, 129, 115, 169, 175, 115, 160, 151, 132, 206, 249, 255, 167, 116, 249, 92, 222, 147, 39, 31, 110, 31, 20, 30, 146, 83, 254, 217, 117, 110, 141, 193, 212, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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