Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2af59000f41e0f26a5a28966072ec879fb7429c59be7a31c75d1dc1ec70cf6c2

Tx prefix hash: 6ebc71af096776ece22820b276beec4f60fba74e6245a587f5f3f38107df5a3a
Tx public key: 8ac088d9f51cf43c0c94b0a11695bb013f248427706d8f5399ec7dc6a2954010
Timestamp: 1706029430 Timestamp [UCT]: 2024-01-23 17:03:50 Age [y:d:h:m:s]: 01:076:23:38:50
Block: 941703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316121 RingCT/type: yes/0
Extra: 018ac088d9f51cf43c0c94b0a11695bb013f248427706d8f5399ec7dc6a295401002110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 772d59e760b34ba99f2f6865860d4d3859246768f4bb2cc0ee6c10dbe4c59b32 0.600000000000 1399859 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": 941713, "vin": [ { "gen": { "height": 941703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "772d59e760b34ba99f2f6865860d4d3859246768f4bb2cc0ee6c10dbe4c59b32" } } ], "extra": [ 1, 138, 192, 136, 217, 245, 28, 244, 60, 12, 148, 176, 161, 22, 149, 187, 1, 63, 36, 132, 39, 112, 109, 143, 83, 153, 236, 125, 198, 162, 149, 64, 16, 2, 17, 0, 0, 0, 4, 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