Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd7863357f70e82767643966f9761b87257b75057103cc45a264ba99dd8910a8

Tx prefix hash: 479b0d4c9e90c0715788be4220f1c0d83c5bcae7b2bf8885ab711319ca8ed5a0
Tx public key: 7a93b85345710d5be6966cc7e215d8b592992e4deab8ed8b6f3a1c74cd823742
Timestamp: 1721600653 Timestamp [UCT]: 2024-07-21 22:24:13 Age [y:d:h:m:s]: 01:152:18:14:15
Block: 1070812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367752 RingCT/type: yes/0
Extra: 017a93b85345710d5be6966cc7e215d8b592992e4deab8ed8b6f3a1c74cd82374202110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: caf4576e880f54a24880afa4afcab87a83de86a6d8f423b1df05f0838eb332fb 0.600000000000 1542803 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": 1070822, "vin": [ { "gen": { "height": 1070812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "caf4576e880f54a24880afa4afcab87a83de86a6d8f423b1df05f0838eb332fb" } } ], "extra": [ 1, 122, 147, 184, 83, 69, 113, 13, 91, 230, 150, 108, 199, 226, 21, 216, 181, 146, 153, 46, 77, 234, 184, 237, 139, 111, 58, 28, 116, 205, 130, 55, 66, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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