Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9ef9263ef1048f4c8d9048131dfb2513fb1f1ea7a3486a283ba517831f53bd6

Tx prefix hash: 236c5c8a17ea4948d704180a01500e5265747f5f2bd1e5ff2acd3f3bd84e7dd9
Tx public key: 0a78b45c8123624411d5fa729e05c6ed06f71427cf8526d515ae10573da47709
Timestamp: 1721073738 Timestamp [UCT]: 2024-07-15 20:02:18 Age [y:d:h:m:s]: 00:191:00:36:03
Block: 1066476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136619 RingCT/type: yes/0
Extra: 010a78b45c8123624411d5fa729e05c6ed06f71427cf8526d515ae10573da47709021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a28d0dfb02db4baa1d60003ad572407553a0e1110cab3538647812217138c5ab 0.600000000000 1537087 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": 1066486, "vin": [ { "gen": { "height": 1066476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a28d0dfb02db4baa1d60003ad572407553a0e1110cab3538647812217138c5ab" } } ], "extra": [ 1, 10, 120, 180, 92, 129, 35, 98, 68, 17, 213, 250, 114, 158, 5, 198, 237, 6, 247, 20, 39, 207, 133, 38, 213, 21, 174, 16, 87, 61, 164, 119, 9, 2, 17, 0, 0, 0, 8, 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