Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ae32b1d934979c71de1747c2e1d5f1876914615abf97029b389b68ed63d155e

Tx prefix hash: be8f5f2e19d844b43f4348cc43fd2102c1efe82821989b208664954aeee4c5bd
Tx public key: e624342ddb5d1dd5428382d2467746a056fbdb50875749218738b9503cf2e11b
Timestamp: 1697130711 Timestamp [UCT]: 2023-10-12 17:11:51 Age [y:d:h:m:s]: 01:091:13:43:01
Block: 868172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326691 RingCT/type: yes/0
Extra: 01e624342ddb5d1dd5428382d2467746a056fbdb50875749218738b9503cf2e11b02110000000b75e3f0e9000000000000000000

1 output(s) for total of 0.815428335000 dcy

stealth address amount amount idx
00: 45a4626b43d22f8c18fdfb17a0c2ee9d00b053a00582230c48a763836ba87aa1 0.815428335000 1322949 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": 868182, "vin": [ { "gen": { "height": 868172 } } ], "vout": [ { "amount": 815428335, "target": { "key": "45a4626b43d22f8c18fdfb17a0c2ee9d00b053a00582230c48a763836ba87aa1" } } ], "extra": [ 1, 230, 36, 52, 45, 219, 93, 29, 213, 66, 131, 130, 210, 70, 119, 70, 160, 86, 251, 219, 80, 135, 87, 73, 33, 135, 56, 185, 80, 60, 242, 225, 27, 2, 17, 0, 0, 0, 11, 117, 227, 240, 233, 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