Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 824d0f6100ff9d0cd8235e9b70da40408e0d0dce928e3291ddb3a8350bdb1dc5

Tx prefix hash: 289d7a38454509f6e3a14a28cab04a91a3366aea22291107906d3d90673806c6
Tx public key: e9d22f68f0ceb284fc2a912d0cc5f32873bc67ffc4202e700d5065d2acf96beb
Timestamp: 1640313791 Timestamp [UCT]: 2021-12-24 02:43:11 Age [y:d:h:m:s]: 03:032:22:30:23
Block: 402185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 802483 RingCT/type: yes/0
Extra: 01e9d22f68f0ceb284fc2a912d0cc5f32873bc67ffc4202e700d5065d2acf96beb0211000000015e327fe8000000000000000000

1 output(s) for total of 28.536091461000 dcy

stealth address amount amount idx
00: d6a12c7c0550398d95e812c1aa977f4cf7ba9836d1195c0b6cbc19fa717ef989 28.536091461000 801892 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": 402195, "vin": [ { "gen": { "height": 402185 } } ], "vout": [ { "amount": 28536091461, "target": { "key": "d6a12c7c0550398d95e812c1aa977f4cf7ba9836d1195c0b6cbc19fa717ef989" } } ], "extra": [ 1, 233, 210, 47, 104, 240, 206, 178, 132, 252, 42, 145, 45, 12, 197, 243, 40, 115, 188, 103, 255, 196, 32, 46, 112, 13, 80, 101, 210, 172, 249, 107, 235, 2, 17, 0, 0, 0, 1, 94, 50, 127, 232, 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