Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbf6c35e9c336f733f8be871a9fbfd55f94df8d9971b804ca89306004cf7abe0

Tx prefix hash: ca9715b1d40f0b103373841c63c845d9a034869bed914aa07501c93b16ed7d7c
Tx public key: 482dcee02cd824e51883d87903dcebeb7441eb24ba524edc2065f96ae0348b31
Timestamp: 1715502682 Timestamp [UCT]: 2024-05-12 08:31:22 Age [y:d:h:m:s]: 00:338:11:46:34
Block: 1020298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241928 RingCT/type: yes/0
Extra: 01482dcee02cd824e51883d87903dcebeb7441eb24ba524edc2065f96ae0348b3102110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c2a26a87ad222f6581a88c1d926fb037b47df250609189d18349f02cf4863db 0.600000000000 1484359 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": 1020308, "vin": [ { "gen": { "height": 1020298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c2a26a87ad222f6581a88c1d926fb037b47df250609189d18349f02cf4863db" } } ], "extra": [ 1, 72, 45, 206, 224, 44, 216, 36, 229, 24, 131, 216, 121, 3, 220, 235, 235, 116, 65, 235, 36, 186, 82, 78, 220, 32, 101, 249, 106, 224, 52, 139, 49, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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