Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: beb5ac9001e8118d1b30132e318a245f259876618850064541a1a838d58d8d1c

Tx prefix hash: f75533d6c318821acf8f9660b7d7ee2e02ef2f4dab21a08d82636c4459b840b7
Tx public key: 89f8381b0ee963b3b51c44bfb37e7559bcf7cd1bf426db93fa1417797b2fa439
Timestamp: 1687617982 Timestamp [UCT]: 2023-06-24 14:46:22 Age [y:d:h:m:s]: 01:209:08:03:56
Block: 789347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410960 RingCT/type: yes/0
Extra: 0189f8381b0ee963b3b51c44bfb37e7559bcf7cd1bf426db93fa1417797b2fa439021100000005faf35c9c000000000000000000

1 output(s) for total of 1.487872994000 dcy

stealth address amount amount idx
00: 1aee213e96c87ef5ed6490d4e9f5d2e4bdcbf27faada593f0c3fd9c1da6432af 1.487872994000 1239560 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": 789357, "vin": [ { "gen": { "height": 789347 } } ], "vout": [ { "amount": 1487872994, "target": { "key": "1aee213e96c87ef5ed6490d4e9f5d2e4bdcbf27faada593f0c3fd9c1da6432af" } } ], "extra": [ 1, 137, 248, 56, 27, 14, 233, 99, 179, 181, 28, 68, 191, 179, 126, 117, 89, 188, 247, 205, 27, 244, 38, 219, 147, 250, 20, 23, 121, 123, 47, 164, 57, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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