Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cbd6e8623d8ca70aa323b025252ef5588adb5565c70397d9ea38b3285128619

Tx prefix hash: 206f6579e6550f94d9d405c204ce1393e4f96ae219b96a743fb027559f1846ad
Tx public key: acde58f897aadf29f3870314dad78723739a19aa81d27e9eedee3e976ed778d9
Timestamp: 1709087150 Timestamp [UCT]: 2024-02-28 02:25:50 Age [y:d:h:m:s]: 01:101:10:15:39
Block: 967092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333544 RingCT/type: yes/0
Extra: 01acde58f897aadf29f3870314dad78723739a19aa81d27e9eedee3e976ed778d902110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8e4b1d7665f3d56c7698e0d1cec30afa9b177c3c6df99f832c2c41a2a0f1221 0.600000000000 1426863 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": 967102, "vin": [ { "gen": { "height": 967092 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8e4b1d7665f3d56c7698e0d1cec30afa9b177c3c6df99f832c2c41a2a0f1221" } } ], "extra": [ 1, 172, 222, 88, 248, 151, 170, 223, 41, 243, 135, 3, 20, 218, 215, 135, 35, 115, 154, 25, 170, 129, 210, 126, 158, 237, 238, 62, 151, 110, 215, 120, 217, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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