Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e16888c2ad7ef0b13571e3d637793fad7c2b625611d7e60d8dd431bef45ce12

Tx prefix hash: 574682757bcb7d09da6fa95e9ddf0bbf0a704a3010c793528ccc62b8ed8d62de
Tx public key: 4e8f402850925a344b405d27c06da1a4f53da09076df0043e741a3f6d670d590
Timestamp: 1632298072 Timestamp [UCT]: 2021-09-22 08:07:52 Age [y:d:h:m:s]: 03:267:19:50:18
Block: 338667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 967326 RingCT/type: yes/0
Extra: 014e8f402850925a344b405d27c06da1a4f53da09076df0043e741a3f6d670d5900211000000143fc41461000000000000000000

1 output(s) for total of 46.329335986000 dcy

stealth address amount amount idx
00: 0f3dfce5a886d6326a62941100456a8537f0a5d84f663623d1cca1f692022f66 46.329335986000 696896 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": 338677, "vin": [ { "gen": { "height": 338667 } } ], "vout": [ { "amount": 46329335986, "target": { "key": "0f3dfce5a886d6326a62941100456a8537f0a5d84f663623d1cca1f692022f66" } } ], "extra": [ 1, 78, 143, 64, 40, 80, 146, 90, 52, 75, 64, 93, 39, 192, 109, 161, 164, 245, 61, 160, 144, 118, 223, 0, 67, 231, 65, 163, 246, 214, 112, 213, 144, 2, 17, 0, 0, 0, 20, 63, 196, 20, 97, 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