Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9214fe86145a0fea9066514c91220b6af419f9687ac1476d46bb4619d541c20a

Tx prefix hash: 19ec1d5e4874ae10ee6defae91a39c5f7fa801ce7b0f2f443045dcbc4e05add2
Tx public key: cfb1793b0d8eb0f36a1a68be096313f8f64fe04d8d724dcff8a40bf6fabe75c5
Timestamp: 1578634939 Timestamp [UCT]: 2020-01-10 05:42:19 Age [y:d:h:m:s]: 05:100:06:36:57
Block: 42238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1221901 RingCT/type: yes/0
Extra: 01cfb1793b0d8eb0f36a1a68be096313f8f64fe04d8d724dcff8a40bf6fabe75c50211000000084943cd9f000000000000000000

1 output(s) for total of 444.681248703000 dcy

stealth address amount amount idx
00: acb112c27fb82cce9b6cf154ab0873f5bb0b5846cbb1b57b98cfdfe90df094fa 444.681248703000 76007 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": 42248, "vin": [ { "gen": { "height": 42238 } } ], "vout": [ { "amount": 444681248703, "target": { "key": "acb112c27fb82cce9b6cf154ab0873f5bb0b5846cbb1b57b98cfdfe90df094fa" } } ], "extra": [ 1, 207, 177, 121, 59, 13, 142, 176, 243, 106, 26, 104, 190, 9, 99, 19, 248, 246, 79, 224, 77, 141, 114, 77, 207, 248, 164, 11, 246, 250, 190, 117, 197, 2, 17, 0, 0, 0, 8, 73, 67, 205, 159, 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