Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f23eab812f1cefff0013033169fbf417e3ab4e15f371bf550a54a7383d55cae6

Tx prefix hash: e6e089ac74a751dc21bbb0ec56c2b6d95276d6a35e44f8e0ca0bd6e864ead122
Tx public key: 43f4d817c041973b820d8672f6179a29195bb842f6fa9d5868ca69afba925f77
Timestamp: 1698330640 Timestamp [UCT]: 2023-10-26 14:30:40 Age [y:d:h:m:s]: 01:019:19:37:16
Block: 878126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275332 RingCT/type: yes/0
Extra: 0143f4d817c041973b820d8672f6179a29195bb842f6fa9d5868ca69afba925f77021100000001faf35c9c000000000000000000

1 output(s) for total of 0.755795062000 dcy

stealth address amount amount idx
00: a81536cedc2da399f91dbd12b9063cc1f5b5f8b1d9bb8ac611c928e72a161972 0.755795062000 1333540 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": 878136, "vin": [ { "gen": { "height": 878126 } } ], "vout": [ { "amount": 755795062, "target": { "key": "a81536cedc2da399f91dbd12b9063cc1f5b5f8b1d9bb8ac611c928e72a161972" } } ], "extra": [ 1, 67, 244, 216, 23, 192, 65, 151, 59, 130, 13, 134, 114, 246, 23, 154, 41, 25, 91, 184, 66, 246, 250, 157, 88, 104, 202, 105, 175, 186, 146, 95, 119, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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