Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae50a9c76adb9c9e3fab2c2fbc93174a268107dc13bfcd047ff39209906e0c4c

Tx prefix hash: f431f3b7d13ca3d2df951aab887041d529a5fe95b81c8318fcd5dc6d45a28932
Tx public key: 985fee8267c5674d7ec3e5a5d00afcbf8393fef3c874ab98ae0e76f577f2f1e4
Timestamp: 1574499326 Timestamp [UCT]: 2019-11-23 08:55:26 Age [y:d:h:m:s]: 05:074:02:48:41
Block: 15326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1195852 RingCT/type: yes/0
Extra: 01985fee8267c5674d7ec3e5a5d00afcbf8393fef3c874ab98ae0e76f577f2f1e4021100000015b63f0b49000000000000000000

1 output(s) for total of 546.033745664000 dcy

stealth address amount amount idx
00: 475db744a4884b76a7fb1125e53d2cded357038ed45a6fa14462c01e9649839d 546.033745664000 20424 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": 15336, "vin": [ { "gen": { "height": 15326 } } ], "vout": [ { "amount": 546033745664, "target": { "key": "475db744a4884b76a7fb1125e53d2cded357038ed45a6fa14462c01e9649839d" } } ], "extra": [ 1, 152, 95, 238, 130, 103, 197, 103, 77, 126, 195, 229, 165, 208, 10, 252, 191, 131, 147, 254, 243, 200, 116, 171, 152, 174, 14, 118, 245, 119, 242, 241, 228, 2, 17, 0, 0, 0, 21, 182, 63, 11, 73, 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