Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f60cd964e76c143cd9a9cd7304ad343c8cacd0dbbd8e59870edfae99ca590a13

Tx prefix hash: be55d8b2c34d6e6e36573c250a9656fa3ed2fcc7572459e58f95e3dc2d08ed4e
Tx public key: 0cc54adbab2e4e12a6396d972e0e6ba5c59cbeb625325dffccd004d5b0437180
Timestamp: 1704887974 Timestamp [UCT]: 2024-01-10 11:59:34 Age [y:d:h:m:s]: 01:084:13:33:00
Block: 932261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321532 RingCT/type: yes/0
Extra: 010cc54adbab2e4e12a6396d972e0e6ba5c59cbeb625325dffccd004d5b04371800211000000029da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 087296209a0c8e35e01503526e9a0379c106137f7fd67c9a26a636412ab68cef 0.600000000000 1390191 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": 932271, "vin": [ { "gen": { "height": 932261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "087296209a0c8e35e01503526e9a0379c106137f7fd67c9a26a636412ab68cef" } } ], "extra": [ 1, 12, 197, 74, 219, 171, 46, 78, 18, 166, 57, 109, 151, 46, 14, 107, 165, 197, 156, 190, 182, 37, 50, 93, 255, 204, 208, 4, 213, 176, 67, 113, 128, 2, 17, 0, 0, 0, 2, 157, 168, 225, 52, 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