Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6c06adfcb852be58536fe7ab0379c7ea04368d25ddf6bf433189631b413d2aa

Tx prefix hash: b4ceb958395ff1d4f15731286be0cb3689a9108d4b796cfa0999891d4e2aa19c
Tx public key: c8455d9fc5601f848062339f92943e82ea9605b446d86bc876a4ae07a499c6a9
Timestamp: 1735813739 Timestamp [UCT]: 2025-01-02 10:28:59 Age [y:d:h:m:s]: 00:167:17:27:51
Block: 1188530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119559 RingCT/type: yes/0
Extra: 01c8455d9fc5601f848062339f92943e82ea9605b446d86bc876a4ae07a499c6a9021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c67ed72c0a5ead640ff03dcfcad0cd93af375f4c10d59b1d7fd105241893a09 0.600000000000 1675031 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": 1188540, "vin": [ { "gen": { "height": 1188530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c67ed72c0a5ead640ff03dcfcad0cd93af375f4c10d59b1d7fd105241893a09" } } ], "extra": [ 1, 200, 69, 93, 159, 197, 96, 31, 132, 128, 98, 51, 159, 146, 148, 62, 130, 234, 150, 5, 180, 70, 216, 107, 200, 118, 164, 174, 7, 164, 153, 198, 169, 2, 17, 0, 0, 0, 2, 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