Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 676ea7d51a40300f08c49260365b8428b7fb3b9806b87604d4e5f53a557f8d1d

Tx prefix hash: 3b254b25b95766bd73b84c4f43200166881ab73e4fcf50b6b32799447f69d87b
Tx public key: 71f3c4f6e8b01e6de76dcd1f9d64a10a63aa85a4c490d120d6d1b6caa8452162
Timestamp: 1719269262 Timestamp [UCT]: 2024-06-24 22:47:42 Age [y:d:h:m:s]: 00:268:15:40:03
Block: 1051487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191998 RingCT/type: yes/0
Extra: 0171f3c4f6e8b01e6de76dcd1f9d64a10a63aa85a4c490d120d6d1b6caa84521620211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a38351de517be5f9c44eedb3b7f9ccd0a222961fac04503a748bc8c2475534d 0.600000000000 1521800 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": 1051497, "vin": [ { "gen": { "height": 1051487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a38351de517be5f9c44eedb3b7f9ccd0a222961fac04503a748bc8c2475534d" } } ], "extra": [ 1, 113, 243, 196, 246, 232, 176, 30, 109, 231, 109, 205, 31, 157, 100, 161, 10, 99, 170, 133, 164, 196, 144, 209, 32, 214, 209, 182, 202, 168, 69, 33, 98, 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