Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c5d8b1fe0d0c663f77380cbda63767bfc05f17287944da9e9943cba4c370e8d

Tx prefix hash: c64b732792b3d1673ccb84fea2ed71dffb02862533220377bf38b9a8c135be16
Tx public key: d3380f719063f90c1bedfdcfac751292df73bffc12fc5e33e974d7eba882e6be
Timestamp: 1703294470 Timestamp [UCT]: 2023-12-23 01:21:10 Age [y:d:h:m:s]: 01:020:06:39:37
Block: 919056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275837 RingCT/type: yes/0
Extra: 01d3380f719063f90c1bedfdcfac751292df73bffc12fc5e33e974d7eba882e6be02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a7088060e83d81d0a3406771e93ed2a8b6ed601199946961a5b4dcb9b6b536c 0.600000000000 1376720 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": 919066, "vin": [ { "gen": { "height": 919056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a7088060e83d81d0a3406771e93ed2a8b6ed601199946961a5b4dcb9b6b536c" } } ], "extra": [ 1, 211, 56, 15, 113, 144, 99, 249, 12, 27, 237, 253, 207, 172, 117, 18, 146, 223, 115, 191, 252, 18, 252, 94, 51, 233, 116, 215, 235, 168, 130, 230, 190, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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