Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aeb3646ab662e5394bd96cdfa59170816e7b99b1939b4fd1be8e0eb76221b7d8

Tx prefix hash: 69528829eb82997028ffdc3425bf3b47961ddd8d122a5a456149916a3956900a
Tx public key: 8ae3de4ec4ae4ced971265f4ae99f65769d0533f87f2cd933c8e3011c2752bbc
Timestamp: 1712214849 Timestamp [UCT]: 2024-04-04 07:14:09 Age [y:d:h:m:s]: 00:223:03:19:08
Block: 992985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159772 RingCT/type: yes/0
Extra: 018ae3de4ec4ae4ced971265f4ae99f65769d0533f87f2cd933c8e3011c2752bbc02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b0e7d438689c181b21f087597aa9b2f7996caf3de42b6a8367a4755ee694fa8 0.600000000000 1453363 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": 992995, "vin": [ { "gen": { "height": 992985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b0e7d438689c181b21f087597aa9b2f7996caf3de42b6a8367a4755ee694fa8" } } ], "extra": [ 1, 138, 227, 222, 78, 196, 174, 76, 237, 151, 18, 101, 244, 174, 153, 246, 87, 105, 208, 83, 63, 135, 242, 205, 147, 60, 142, 48, 17, 194, 117, 43, 188, 2, 17, 0, 0, 0, 4, 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