Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e724430385c55c56f3ce41ffa243200418174e0a6f12fa25cf7b5d1e9723ff3

Tx prefix hash: 528dc4dda886a3c376e662d28f1e03f907e2c9d032ab3239f64bb34f9ebeb0b6
Tx public key: ddb0baf25df3217e060dffc31b92190a08ca63941d039934d6c094b8daeab4a0
Timestamp: 1706502025 Timestamp [UCT]: 2024-01-29 04:20:25 Age [y:d:h:m:s]: 00:353:19:18:53
Block: 945628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253299 RingCT/type: yes/0
Extra: 01ddb0baf25df3217e060dffc31b92190a08ca63941d039934d6c094b8daeab4a00211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25917afeb9783d1e44a3a80deb5277971e9ae219880c5f7e8d0407ee7311f8a5 0.600000000000 1403944 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": 945638, "vin": [ { "gen": { "height": 945628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25917afeb9783d1e44a3a80deb5277971e9ae219880c5f7e8d0407ee7311f8a5" } } ], "extra": [ 1, 221, 176, 186, 242, 93, 243, 33, 126, 6, 13, 255, 195, 27, 146, 25, 10, 8, 202, 99, 148, 29, 3, 153, 52, 214, 192, 148, 184, 218, 234, 180, 160, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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