Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc4a46a34fbc7654a7b2e3c45dc40e45bc00ce28711f884856b5b9c9422cc991

Tx prefix hash: 55f5b23bb85f229f72249086f87e94539940cb403e18a4a587bd388a43b29cfd
Tx public key: 50641da60d5c5e6d99964e1310951a6b39a5de1f1ad8409e7c9cc232d0ef40a4
Timestamp: 1725574228 Timestamp [UCT]: 2024-09-05 22:10:28 Age [y:d:h:m:s]: 00:125:11:02:02
Block: 1103776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89721 RingCT/type: yes/0
Extra: 0150641da60d5c5e6d99964e1310951a6b39a5de1f1ad8409e7c9cc232d0ef40a4021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea1a578bb0cecf0c520cbc55570a84c888f9eade2401bd1ed9ae25c3fa282770 0.600000000000 1580733 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": 1103786, "vin": [ { "gen": { "height": 1103776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea1a578bb0cecf0c520cbc55570a84c888f9eade2401bd1ed9ae25c3fa282770" } } ], "extra": [ 1, 80, 100, 29, 166, 13, 92, 94, 109, 153, 150, 78, 19, 16, 149, 26, 107, 57, 165, 222, 31, 26, 216, 64, 158, 124, 156, 194, 50, 208, 239, 64, 164, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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