Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cc89770cd4dde89b372db7c16dcacb101e7306211527f2d5117f065efab0e14

Tx prefix hash: 974a5467c7c6349e5ca64412808f4b8163d69515eb7157a3f0b119b06d5c27ce
Tx public key: 94abc73d5269c3f7fcc0fe75eb34b045abb4f081789a82f4fb34fa902f54c5c9
Timestamp: 1736970264 Timestamp [UCT]: 2025-01-15 19:44:24 Age [y:d:h:m:s]: 00:153:21:26:02
Block: 1198094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109698 RingCT/type: yes/0
Extra: 0194abc73d5269c3f7fcc0fe75eb34b045abb4f081789a82f4fb34fa902f54c5c90211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e9591c0571b4605c618aaaf3599a37c0586a1d2b1cf8c443bf044314e867d67 0.600000000000 1684713 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": 1198104, "vin": [ { "gen": { "height": 1198094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e9591c0571b4605c618aaaf3599a37c0586a1d2b1cf8c443bf044314e867d67" } } ], "extra": [ 1, 148, 171, 199, 61, 82, 105, 195, 247, 252, 192, 254, 117, 235, 52, 176, 69, 171, 180, 240, 129, 120, 154, 130, 244, 251, 52, 250, 144, 47, 84, 197, 201, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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