Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1917b35a58f6f9f262c4f43381e639b0cef83052cead8ba1dda63623f8196c03

Tx prefix hash: 972c884e31661ec3de9e79db02f63a23be312a40acffa34baeb0585202e74ff8
Tx public key: 6b778447625b3d2c8e49ff354c0dc2d83d41276d44b21c2c3e5b58cbf7d634ac
Timestamp: 1750768559 Timestamp [UCT]: 2025-06-24 12:35:59 Age [y:d:h:m:s]: 00:180:20:22:53
Block: 1311812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127227 RingCT/type: yes/0
Extra: 016b778447625b3d2c8e49ff354c0dc2d83d41276d44b21c2c3e5b58cbf7d634ac0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73cc384ba681c25c699f2ea85a16cf17eec28143e14e6015aff1ebe8506308fb 0.600000000000 1799441 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": 1311822, "vin": [ { "gen": { "height": 1311812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73cc384ba681c25c699f2ea85a16cf17eec28143e14e6015aff1ebe8506308fb" } } ], "extra": [ 1, 107, 119, 132, 71, 98, 91, 61, 44, 142, 73, 255, 53, 76, 13, 194, 216, 61, 65, 39, 109, 68, 178, 28, 44, 62, 91, 88, 203, 247, 214, 52, 172, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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