Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acc4ea3d2b6540459ec50a9a07429fa5a926b763a19e36a4578d36e50ebb1d17

Tx prefix hash: c90bf8eb34e5e5937c0bb512f17aecd1855d0900ba69f439bb7a3e531e7ffaed
Tx public key: 86bc2ee4b990f0ee32fd5c3be7bbbc6c3ef179a0b04774132bab6bd2aa8d56b4
Timestamp: 1733214200 Timestamp [UCT]: 2024-12-03 08:23:20 Age [y:d:h:m:s]: 00:123:21:34:01
Block: 1167005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88358 RingCT/type: yes/0
Extra: 0186bc2ee4b990f0ee32fd5c3be7bbbc6c3ef179a0b04774132bab6bd2aa8d56b4021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a57ecd9496eb85aba69706607acc79db0855aa8d8aa7ef62a988600a6d6002f5 0.600000000000 1652698 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": 1167015, "vin": [ { "gen": { "height": 1167005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a57ecd9496eb85aba69706607acc79db0855aa8d8aa7ef62a988600a6d6002f5" } } ], "extra": [ 1, 134, 188, 46, 228, 185, 144, 240, 238, 50, 253, 92, 59, 231, 187, 188, 108, 62, 241, 121, 160, 176, 71, 116, 19, 43, 171, 107, 210, 170, 141, 86, 180, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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