Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6a4101a92a051420db34d4b60d4d091f7cacb84e896c27cb4592ffe6e12c6ec

Tx prefix hash: e085a31f16dfe3fe6913e47fd4f193d3bdbfbb733f95769b527932e713580be4
Tx public key: a857e1569bd8b491e9a3dc5d1f8b0514c4cc71d4f046658ba6b0752f56670718
Timestamp: 1583857810 Timestamp [UCT]: 2020-03-10 16:30:10 Age [y:d:h:m:s]: 05:236:03:44:50
Block: 80006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1322158 RingCT/type: yes/0
Extra: 01a857e1569bd8b491e9a3dc5d1f8b0514c4cc71d4f046658ba6b0752f56670718021100000006c48ea382000000000000000000

1 output(s) for total of 333.355557541000 dcy

stealth address amount amount idx
00: 9a920aa20136d4cd71fdbffea372e83c334b8a179b18e900ce3dc70bf61198fb 333.355557541000 146384 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": 80016, "vin": [ { "gen": { "height": 80006 } } ], "vout": [ { "amount": 333355557541, "target": { "key": "9a920aa20136d4cd71fdbffea372e83c334b8a179b18e900ce3dc70bf61198fb" } } ], "extra": [ 1, 168, 87, 225, 86, 155, 216, 180, 145, 233, 163, 220, 93, 31, 139, 5, 20, 196, 204, 113, 212, 240, 70, 101, 139, 166, 176, 117, 47, 86, 103, 7, 24, 2, 17, 0, 0, 0, 6, 196, 142, 163, 130, 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