Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1d5f55591e09b5ede0b9182050ffa45db6e9956d0ce0a8bde3460e5f1847c0a

Tx prefix hash: b4f0d5a8fa8d5270d016f1186272f634a46c8e7f009f729f41fb33562cf4e937
Tx public key: 8160bc0e47c2308557a89089e62ae9ffa5f3131f71b653445542b37b772f0d33
Timestamp: 1734337826 Timestamp [UCT]: 2024-12-16 08:30:26 Age [y:d:h:m:s]: 00:095:17:37:12
Block: 1176331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68187 RingCT/type: yes/0
Extra: 018160bc0e47c2308557a89089e62ae9ffa5f3131f71b653445542b37b772f0d33021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6ea75d09a9c976097504014037f2567dd2014f40b7c4359b3dc9d8dce753d4e 0.600000000000 1662662 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": 1176341, "vin": [ { "gen": { "height": 1176331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6ea75d09a9c976097504014037f2567dd2014f40b7c4359b3dc9d8dce753d4e" } } ], "extra": [ 1, 129, 96, 188, 14, 71, 194, 48, 133, 87, 168, 144, 137, 230, 42, 233, 255, 165, 243, 19, 31, 113, 182, 83, 68, 85, 66, 179, 123, 119, 47, 13, 51, 2, 17, 0, 0, 0, 7, 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