Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6118d845290c1b265ca75f91d47638937b5e7d8293e18344230158c1cb5274f3

Tx prefix hash: 0ec5de285565a358a3d662d21f204da7a67d16b3a230599fa5c48465e57d749a
Tx public key: 57d719c87eafe6c1c2add737f424b83aec8e2721c1cac7711d20448901d11dca
Timestamp: 1726378445 Timestamp [UCT]: 2024-09-15 05:34:05 Age [y:d:h:m:s]: 00:070:12:00:22
Block: 1110432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50402 RingCT/type: yes/0
Extra: 0157d719c87eafe6c1c2add737f424b83aec8e2721c1cac7711d20448901d11dca021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 953a87dce2aa84e0dfb930d12a7ce095ea2426ed3a1921c969e64afd40064fd5 0.600000000000 1589037 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": 1110442, "vin": [ { "gen": { "height": 1110432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "953a87dce2aa84e0dfb930d12a7ce095ea2426ed3a1921c969e64afd40064fd5" } } ], "extra": [ 1, 87, 215, 25, 200, 126, 175, 230, 193, 194, 173, 215, 55, 244, 36, 184, 58, 236, 142, 39, 33, 193, 202, 199, 113, 29, 32, 68, 137, 1, 209, 29, 202, 2, 17, 0, 0, 0, 9, 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