Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08562f96e6798d4f6befb17242216c1ee3decb2a4fbe429a60d426cdbac87a9a

Tx prefix hash: d52e61e0356c9740ea13e3f0c8f74b4a920804d5db667e98281f944d583a4fa6
Tx public key: 48e7ab2a7a1416c37b7db6c175a162e9bc0334301c71e030fa0ebb513778331c
Timestamp: 1728077459 Timestamp [UCT]: 2024-10-04 21:30:59 Age [y:d:h:m:s]: 00:186:12:01:17
Block: 1124523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133089 RingCT/type: yes/0
Extra: 0148e7ab2a7a1416c37b7db6c175a162e9bc0334301c71e030fa0ebb513778331c021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b74ce4e1251d3527ca405a2b737ca035c9ec22598d110c4cadfc1d20e62e1bbd 0.600000000000 1607158 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": 1124533, "vin": [ { "gen": { "height": 1124523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b74ce4e1251d3527ca405a2b737ca035c9ec22598d110c4cadfc1d20e62e1bbd" } } ], "extra": [ 1, 72, 231, 171, 42, 122, 20, 22, 195, 123, 125, 182, 193, 117, 161, 98, 233, 188, 3, 52, 48, 28, 113, 224, 48, 250, 14, 187, 81, 55, 120, 51, 28, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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