Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ef16b9179ad40831106ea5d1b2f1fb866dc34615b432f52167f75b32d37a9fc

Tx prefix hash: 7fdcbffe50d9ed6e882410c6b11bf41c270afbac6921ba23696c91fa5cc58515
Tx public key: f95a8d5f6e37c08577d793d0e8ca28818fd5943d0f4e9ccf4fc75eb5c84b3f0a
Timestamp: 1578254146 Timestamp [UCT]: 2020-01-05 19:55:46 Age [y:d:h:m:s]: 04:305:11:03:28
Block: 39429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107490 RingCT/type: yes/0
Extra: 01f95a8d5f6e37c08577d793d0e8ca28818fd5943d0f4e9ccf4fc75eb5c84b3f0a02110000014949b77a3d000000000000000000

1 output(s) for total of 454.321927462000 dcy

stealth address amount amount idx
00: 04af67fd6a15dc57c8bc1e2003ee6649de45190c4095fe57671c0203d1d31f81 454.321927462000 68013 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": 39439, "vin": [ { "gen": { "height": 39429 } } ], "vout": [ { "amount": 454321927462, "target": { "key": "04af67fd6a15dc57c8bc1e2003ee6649de45190c4095fe57671c0203d1d31f81" } } ], "extra": [ 1, 249, 90, 141, 95, 110, 55, 192, 133, 119, 215, 147, 208, 232, 202, 40, 129, 143, 213, 148, 61, 15, 78, 156, 207, 79, 199, 94, 181, 200, 75, 63, 10, 2, 17, 0, 0, 1, 73, 73, 183, 122, 61, 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