Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f10f62e10baa56b286ca0e0a897e8b94300062a084ce4f54d9fc9857da0010e

Tx prefix hash: 96a4d8345777337c6e52f6bf0484f60a55682e26bcbbc41f5f1a2bbf0c036eb0
Tx public key: 0e3782abee5346031907dfd7363695c11a8a07c55315b037e8827d0130915329
Timestamp: 1588566434 Timestamp [UCT]: 2020-05-04 04:27:14 Age [y:d:h:m:s]: 04:196:17:15:37
Block: 98418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1056101 RingCT/type: yes/0
Extra: 010e3782abee5346031907dfd7363695c11a8a07c55315b037e8827d013091532902110000001b8a2ee0d9000000000000000000

1 output(s) for total of 289.673379637000 dcy

stealth address amount amount idx
00: 395295d97d901102d34c9b28170a9be9e37dc29003974513122501a27f17e2ba 289.673379637000 173921 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": 98428, "vin": [ { "gen": { "height": 98418 } } ], "vout": [ { "amount": 289673379637, "target": { "key": "395295d97d901102d34c9b28170a9be9e37dc29003974513122501a27f17e2ba" } } ], "extra": [ 1, 14, 55, 130, 171, 238, 83, 70, 3, 25, 7, 223, 215, 54, 54, 149, 193, 26, 138, 7, 197, 83, 21, 176, 55, 232, 130, 125, 1, 48, 145, 83, 41, 2, 17, 0, 0, 0, 27, 138, 46, 224, 217, 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