Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b30707bd39cd38256c2598344b4077ae04dd912f560ba0cb96d6d315ac351476

Tx prefix hash: 7126711a05253f271786b1b77bc58ab549e1a7f9cab6535c11d9bc0b94e45b46
Tx public key: f600bbd90c3a909fb32afdc3f8263e8f93ac9b7d172993e86524c6fbcb96f760
Timestamp: 1720596097 Timestamp [UCT]: 2024-07-10 07:21:37 Age [y:d:h:m:s]: 00:198:02:22:25
Block: 1062508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141695 RingCT/type: yes/0
Extra: 01f600bbd90c3a909fb32afdc3f8263e8f93ac9b7d172993e86524c6fbcb96f760021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a23439d18a0411eee0e0bbce849bdab2d3cbd4aeaa9701c1e49d74476e57210 0.600000000000 1533011 of 15

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": 1062518, "vin": [ { "gen": { "height": 1062508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a23439d18a0411eee0e0bbce849bdab2d3cbd4aeaa9701c1e49d74476e57210" } } ], "extra": [ 1, 246, 0, 187, 217, 12, 58, 144, 159, 179, 42, 253, 195, 248, 38, 62, 143, 147, 172, 155, 125, 23, 41, 147, 232, 101, 36, 198, 251, 203, 150, 247, 96, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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