Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d47d29ec92cfba13f70d27795376192684b15f614ca8f5e4373f4e482c16eda7

Tx prefix hash: 0053e9aec895f58296e44a9a026e06d97240c0d77dc1cad4f0c9c3677b18a348
Tx public key: 9f31adecc87f2b01c07287ac96d7d1d9f1abe931be563aa732c3cbf605a33dc7
Timestamp: 1702854487 Timestamp [UCT]: 2023-12-17 23:08:07 Age [y:d:h:m:s]: 01:033:12:28:58
Block: 915410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285272 RingCT/type: yes/0
Extra: 019f31adecc87f2b01c07287ac96d7d1d9f1abe931be563aa732c3cbf605a33dc7021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdf5b1c5a21fd550e8e71be2f3ad1c741f4c1f59496e59da3a5ecb0f3d7347ad 0.600000000000 1372806 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": 915420, "vin": [ { "gen": { "height": 915410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdf5b1c5a21fd550e8e71be2f3ad1c741f4c1f59496e59da3a5ecb0f3d7347ad" } } ], "extra": [ 1, 159, 49, 173, 236, 200, 127, 43, 1, 192, 114, 135, 172, 150, 215, 209, 217, 241, 171, 233, 49, 190, 86, 58, 167, 50, 195, 203, 246, 5, 163, 61, 199, 2, 17, 0, 0, 0, 2, 250, 243, 92, 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