Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09172b860f3506047f06f815432c28b8e64206908438a463bd91ca2eb3d58845

Tx prefix hash: bb196a5de99066d718887f46aec12f0fcef99b59d6e99d15aebf9a0d4d03bffc
Tx public key: 8a9c08e0fda0311d49d8091e21b03fd6c552ef4abdb1cb83eba06ab6a5421064
Timestamp: 1716512916 Timestamp [UCT]: 2024-05-24 01:08:36 Age [y:d:h:m:s]: 01:010:03:17:14
Block: 1028654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268155 RingCT/type: yes/0
Extra: 018a9c08e0fda0311d49d8091e21b03fd6c552ef4abdb1cb83eba06ab6a542106402110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a35b01936632bd00193ed30acce03b5e8defc8ba1e79a8b0b5606d3c41188b0d 0.600000000000 1496649 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": 1028664, "vin": [ { "gen": { "height": 1028654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a35b01936632bd00193ed30acce03b5e8defc8ba1e79a8b0b5606d3c41188b0d" } } ], "extra": [ 1, 138, 156, 8, 224, 253, 160, 49, 29, 73, 216, 9, 30, 33, 176, 63, 214, 197, 82, 239, 74, 189, 177, 203, 131, 235, 160, 106, 182, 165, 66, 16, 100, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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