Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f7d9d055332a26240136ec6f8b9269492e827ebe7ddad44219864f88eb2d0ec

Tx prefix hash: 90d117cf450cf3f89e5857b1d10a47acf7648b2affab322b18a9b0beb8ce1fec
Tx public key: fb685c52b106b33b8cc6b7a95d5133b607d0fb59c288ce508f0435b7797f4971
Timestamp: 1677895780 Timestamp [UCT]: 2023-03-04 02:09:40 Age [y:d:h:m:s]: 02:028:23:11:52
Block: 709379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 542264 RingCT/type: yes/0
Extra: 01fb685c52b106b33b8cc6b7a95d5133b607d0fb59c288ce508f0435b7797f49710211000000025029cbac000000000000000000

1 output(s) for total of 2.738626431000 dcy

stealth address amount amount idx
00: 34e2161312a1d8a4dffd433c71b5a49a695be7bea8cd0c014aa2ec526358ed61 2.738626431000 1153360 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": 709389, "vin": [ { "gen": { "height": 709379 } } ], "vout": [ { "amount": 2738626431, "target": { "key": "34e2161312a1d8a4dffd433c71b5a49a695be7bea8cd0c014aa2ec526358ed61" } } ], "extra": [ 1, 251, 104, 92, 82, 177, 6, 179, 59, 140, 198, 183, 169, 93, 81, 51, 182, 7, 208, 251, 89, 194, 136, 206, 80, 143, 4, 53, 183, 121, 127, 73, 113, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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