Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92f6029931f424360e5ce659d902e393b6f13ef95ce41a3c585f599658e61d64

Tx prefix hash: af6241c9ef10bc4b9a55899f9bf701b4f8101c01c77da2521de961f5896f8a7e
Tx public key: 7f689e0d2f518f57a3665703fcd63cb3bf2a2d85c2efd7c9babf81bd4429d5e7
Timestamp: 1712456415 Timestamp [UCT]: 2024-04-07 02:20:15 Age [y:d:h:m:s]: 01:051:14:15:55
Block: 994981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297900 RingCT/type: yes/0
Extra: 017f689e0d2f518f57a3665703fcd63cb3bf2a2d85c2efd7c9babf81bd4429d5e702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51a2e87248e1b5ba2718fb661912b1d3f2971aa83d1dfd70fc1cdc3608d53c5a 0.600000000000 1455385 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": 994991, "vin": [ { "gen": { "height": 994981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51a2e87248e1b5ba2718fb661912b1d3f2971aa83d1dfd70fc1cdc3608d53c5a" } } ], "extra": [ 1, 127, 104, 158, 13, 47, 81, 143, 87, 163, 102, 87, 3, 252, 214, 60, 179, 191, 42, 45, 133, 194, 239, 215, 201, 186, 191, 129, 189, 68, 41, 213, 231, 2, 17, 0, 0, 0, 2, 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