Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8b74b076a2b93062fbb3a37fd08a5b098efba26595a704dcc08fee3e2e867e3

Tx prefix hash: 125a2f4688be9d0f4c4c91169da7cc642e153eb82620dccbea0617356ced85a3
Tx public key: 41d173c75452451d8fd9e9a78050c203adfdafecc53b9cbee3c855696b50cd77
Timestamp: 1714229343 Timestamp [UCT]: 2024-04-27 14:49:03 Age [y:d:h:m:s]: 00:211:11:50:21
Block: 1009710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151399 RingCT/type: yes/0
Extra: 0141d173c75452451d8fd9e9a78050c203adfdafecc53b9cbee3c855696b50cd7702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1c42c4b17b3179724a71ba6fbec46daa277b373d0a3a917d9266befba690a91 0.600000000000 1471458 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": 1009720, "vin": [ { "gen": { "height": 1009710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1c42c4b17b3179724a71ba6fbec46daa277b373d0a3a917d9266befba690a91" } } ], "extra": [ 1, 65, 209, 115, 199, 84, 82, 69, 29, 143, 217, 233, 167, 128, 80, 194, 3, 173, 253, 175, 236, 197, 59, 156, 190, 227, 200, 85, 105, 107, 80, 205, 119, 2, 17, 0, 0, 0, 1, 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