Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4f79197269b57f3f6f927861f44296590bc4162043b820c04702c724bf3b251

Tx prefix hash: 961819406d1406659020e48ecb0e282d8934152b56b651e28dd87dc2c57e0ced
Tx public key: 6c4c07dc65df2624b0d6c125754b689aad8d0d6a34699cd44f843c28c27db2f4
Timestamp: 1747213828 Timestamp [UCT]: 2025-05-14 09:10:28 Age [y:d:h:m:s]: 00:189:17:04:56
Block: 1282647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133290 RingCT/type: yes/0
Extra: 016c4c07dc65df2624b0d6c125754b689aad8d0d6a34699cd44f843c28c27db2f40211000000069f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59ddcde4f359dac3e95ca9b63f421f38ed2855985d5fb50e92900f6f3615b1d8 0.600000000000 1770054 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": 1282657, "vin": [ { "gen": { "height": 1282647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59ddcde4f359dac3e95ca9b63f421f38ed2855985d5fb50e92900f6f3615b1d8" } } ], "extra": [ 1, 108, 76, 7, 220, 101, 223, 38, 36, 176, 214, 193, 37, 117, 75, 104, 154, 173, 141, 13, 106, 52, 105, 156, 212, 79, 132, 60, 40, 194, 125, 178, 244, 2, 17, 0, 0, 0, 6, 159, 159, 230, 140, 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