Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc6c5b36fe6d418114fb3b6fc1873db3990c5911440860577c0d56ac85a953d3

Tx prefix hash: 29233ff4729d49e67cafae5614ec1de319944d55333bc9141bd2d7e6e6db2fee
Tx public key: 85d5feb0bbb6e5631c212275cc5b408f3471039152c71e0a1242145b54e37ebf
Timestamp: 1704152276 Timestamp [UCT]: 2024-01-01 23:37:56 Age [y:d:h:m:s]: 01:166:19:25:51
Block: 926159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380267 RingCT/type: yes/0
Extra: 0185d5feb0bbb6e5631c212275cc5b408f3471039152c71e0a1242145b54e37ebf02110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8b2e65ab5f23b9c9f18c7fbc1abbddfc1e0080aa276269645afbb80980150a8 0.600000000000 1383933 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": 926169, "vin": [ { "gen": { "height": 926159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8b2e65ab5f23b9c9f18c7fbc1abbddfc1e0080aa276269645afbb80980150a8" } } ], "extra": [ 1, 133, 213, 254, 176, 187, 182, 229, 99, 28, 33, 34, 117, 204, 91, 64, 143, 52, 113, 3, 145, 82, 199, 30, 10, 18, 66, 20, 91, 84, 227, 126, 191, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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