Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf0e51ee052d763a45c177a76c91fee2e88740650400bbf84df405be168e7640

Tx prefix hash: 247f3dac97b05cdf8da62f7c3a893f56ffdb8661f1ac56a7783b18af9523b69e
Tx public key: 0a0ffb12e1ed2c82965154a77ea8c28459cb0159ca29620eb4c5939dd9c2029b
Timestamp: 1722669106 Timestamp [UCT]: 2024-08-03 07:11:46 Age [y:d:h:m:s]: 00:206:07:48:42
Block: 1079681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147330 RingCT/type: yes/0
Extra: 010a0ffb12e1ed2c82965154a77ea8c28459cb0159ca29620eb4c5939dd9c2029b02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eec53dd59fa827a8146e7a37b1dfd38d754033b767aa852b4333aeabd9fe2a49 0.600000000000 1552744 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": 1079691, "vin": [ { "gen": { "height": 1079681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eec53dd59fa827a8146e7a37b1dfd38d754033b767aa852b4333aeabd9fe2a49" } } ], "extra": [ 1, 10, 15, 251, 18, 225, 237, 44, 130, 150, 81, 84, 167, 126, 168, 194, 132, 89, 203, 1, 89, 202, 41, 98, 14, 180, 197, 147, 157, 217, 194, 2, 155, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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