Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 708a2dc2224283b779f0b1848cc2de818d94e80b8b7151723b9d54deb6616ed9

Tx prefix hash: 8b0232a714a2fa9f0c329aa64bf0a32b3a1fea35d7e17389d81fc49ff2638956
Tx public key: bff176bbf7c6c8322c73349434d58ad57213be5b8555a801c64472aa3852919d
Timestamp: 1707516212 Timestamp [UCT]: 2024-02-09 22:03:32 Age [y:d:h:m:s]: 01:094:04:43:08
Block: 954047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328400 RingCT/type: yes/0
Extra: 01bff176bbf7c6c8322c73349434d58ad57213be5b8555a801c64472aa3852919d0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e216a0aa5cde1eb8dc090b82f753f59e6074d0f14382c719aca0ce77e449af5 0.600000000000 1413319 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": 954057, "vin": [ { "gen": { "height": 954047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e216a0aa5cde1eb8dc090b82f753f59e6074d0f14382c719aca0ce77e449af5" } } ], "extra": [ 1, 191, 241, 118, 187, 247, 198, 200, 50, 44, 115, 52, 148, 52, 213, 138, 213, 114, 19, 190, 91, 133, 85, 168, 1, 198, 68, 114, 170, 56, 82, 145, 157, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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