Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 070773dbc933792d3bc080bfd94ce2f5be8d5d801c2e61be1dbe4bcc37f14611

Tx prefix hash: 5417bff501d0f4d66e1734731e84619e856dd60e0146d33736f38a385eb0ac65
Tx public key: 42599a96f3c3b3be3f2f0c07b88e824a2ae74c3694982bab2f529ddd7beb3aa9
Timestamp: 1649616285 Timestamp [UCT]: 2022-04-10 18:44:45 Age [y:d:h:m:s]: 02:260:23:04:05
Block: 477443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 706293 RingCT/type: yes/0
Extra: 0142599a96f3c3b3be3f2f0c07b88e824a2ae74c3694982bab2f529ddd7beb3aa9021100000001bf7ee4e7000000000000000000

1 output(s) for total of 16.070647808000 dcy

stealth address amount amount idx
00: d77dc25af6b310dbf4889845dc00ff63816a435e8d47f4a3674de0bb68c9da18 16.070647808000 898106 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": 477453, "vin": [ { "gen": { "height": 477443 } } ], "vout": [ { "amount": 16070647808, "target": { "key": "d77dc25af6b310dbf4889845dc00ff63816a435e8d47f4a3674de0bb68c9da18" } } ], "extra": [ 1, 66, 89, 154, 150, 243, 195, 179, 190, 63, 47, 12, 7, 184, 142, 130, 74, 42, 231, 76, 54, 148, 152, 43, 171, 47, 82, 157, 221, 123, 235, 58, 169, 2, 17, 0, 0, 0, 1, 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