Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78397e378e3fc4575dc93db4440c6352643f82770c3160b7ede094bd27edd9d6

Tx prefix hash: e95a0ec9b9b223029b775ed13b77c1d45e6b2775d8573e2c01cc6351f4cd0b34
Tx public key: 2cd0e7923828dc6a8b066341a48e001a703c9bd786327cf1ad913c9034b4fa7f
Timestamp: 1741246807 Timestamp [UCT]: 2025-03-06 07:40:07 Age [y:d:h:m:s]: 00:006:09:02:42
Block: 1233243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4565 RingCT/type: yes/0
Extra: 012cd0e7923828dc6a8b066341a48e001a703c9bd786327cf1ad913c9034b4fa7f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c2538c02c05d6095aaf68635ff0d0f15405d5cb0aedd8f6e562d603192462a9 0.600000000000 1720162 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": 1233253, "vin": [ { "gen": { "height": 1233243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c2538c02c05d6095aaf68635ff0d0f15405d5cb0aedd8f6e562d603192462a9" } } ], "extra": [ 1, 44, 208, 231, 146, 56, 40, 220, 106, 139, 6, 99, 65, 164, 142, 0, 26, 112, 60, 155, 215, 134, 50, 124, 241, 173, 145, 60, 144, 52, 180, 250, 127, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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