Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b59306194adc8f8ce31648bf1eb9b72782f9d2f388cfa95745a882458e933d78

Tx prefix hash: dd57a98d5ab3323cd14edc7fae71c60af3e2710bbd80090ae5225218d784c13e
Tx public key: 75f20bd90396f96d8bd1183a41aebd50b1817d9a2af45aa8bbeb0726a78e0108
Timestamp: 1657263121 Timestamp [UCT]: 2022-07-08 06:52:01 Age [y:d:h:m:s]: 02:312:22:17:06
Block: 539147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 744788 RingCT/type: yes/0
Extra: 0175f20bd90396f96d8bd1183a41aebd50b1817d9a2af45aa8bbeb0726a78e0108021100000009bf7ee4e7000000000000000000

1 output(s) for total of 10.036500871000 dcy

stealth address amount amount idx
00: 32cf9a7f1a9f3a35604eb544301cdcb9e778885c6ab115255ba44e9f15701abe 10.036500871000 969220 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": 539157, "vin": [ { "gen": { "height": 539147 } } ], "vout": [ { "amount": 10036500871, "target": { "key": "32cf9a7f1a9f3a35604eb544301cdcb9e778885c6ab115255ba44e9f15701abe" } } ], "extra": [ 1, 117, 242, 11, 217, 3, 150, 249, 109, 139, 209, 24, 58, 65, 174, 189, 80, 177, 129, 125, 154, 42, 244, 90, 168, 187, 235, 7, 38, 167, 142, 1, 8, 2, 17, 0, 0, 0, 9, 191, 126, 228, 231, 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