Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a7a4b48fe611631e88e0998dd0dbcd4fd7ea4ea11bbb5c3e1aed95afec57d48

Tx prefix hash: db165bb4b41f1f222b215c5fd53bcf328969da0b74249602a721598fb3fcab8f
Tx public key: e0bfc5600e40f4ff26994cedeff76cb1586ae9e7d943af3cac1dcb99e1b5db54
Timestamp: 1682530581 Timestamp [UCT]: 2023-04-26 17:36:21 Age [y:d:h:m:s]: 02:221:11:48:21
Block: 747165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 678170 RingCT/type: yes/0
Extra: 01e0bfc5600e40f4ff26994cedeff76cb1586ae9e7d943af3cac1dcb99e1b5db540211000000037e406890000000000000000000

1 output(s) for total of 2.052732694000 dcy

stealth address amount amount idx
00: 1275ff7583c285d7756d8d0ec6ec4f0112e7d380214e10cc29dc84c03a53e8bb 2.052732694000 1194808 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": 747175, "vin": [ { "gen": { "height": 747165 } } ], "vout": [ { "amount": 2052732694, "target": { "key": "1275ff7583c285d7756d8d0ec6ec4f0112e7d380214e10cc29dc84c03a53e8bb" } } ], "extra": [ 1, 224, 191, 197, 96, 14, 64, 244, 255, 38, 153, 76, 237, 239, 247, 108, 177, 88, 106, 233, 231, 217, 67, 175, 60, 172, 29, 203, 153, 225, 181, 219, 84, 2, 17, 0, 0, 0, 3, 126, 64, 104, 144, 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