Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38fe0de1b0b9df9f955de74919677562cfb7b47777646b9db1e4e37c8bdb1283

Tx prefix hash: 3be3be5984e041e9f8c3bc64e638291e65fb30ba1636603b5e70b8b0c7aa845f
Tx public key: d5b4deae0f5b436e8c72d1ecc2a9427fd5e5273371557dedad05dc9c34e07fe1
Timestamp: 1700474729 Timestamp [UCT]: 2023-11-20 10:05:29 Age [y:d:h:m:s]: 01:139:21:04:20
Block: 895684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361132 RingCT/type: yes/0
Extra: 01d5b4deae0f5b436e8c72d1ecc2a9427fd5e5273371557dedad05dc9c34e07fe102110000000333af99f4000000000000000000

1 output(s) for total of 0.661038998000 dcy

stealth address amount amount idx
00: e3b5ae0cb11df9c96e20823dec76e16f3b1353e74a327d587887c37cd79ee18e 0.661038998000 1351925 of 0

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": 895694, "vin": [ { "gen": { "height": 895684 } } ], "vout": [ { "amount": 661038998, "target": { "key": "e3b5ae0cb11df9c96e20823dec76e16f3b1353e74a327d587887c37cd79ee18e" } } ], "extra": [ 1, 213, 180, 222, 174, 15, 91, 67, 110, 140, 114, 209, 236, 194, 169, 66, 127, 213, 229, 39, 51, 113, 85, 125, 237, 173, 5, 220, 156, 52, 224, 127, 225, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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