Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa7f06871d12b18c7de2fb85a32e9f5af866524b46673c1c063e40037a6ba841

Tx prefix hash: 7b191b30772686d41260668aa97c47e51096ed4fbfce07ea3842d8fc3780cd67
Tx public key: 2985bf6608a7235ae88374048b6d87c54a6b47e9c40a8332f292aeeda4a72525
Timestamp: 1718723298 Timestamp [UCT]: 2024-06-18 15:08:18 Age [y:d:h:m:s]: 00:328:14:30:06
Block: 1046969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234846 RingCT/type: yes/0
Extra: 012985bf6608a7235ae88374048b6d87c54a6b47e9c40a8332f292aeeda4a7252502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a2feafa60e8fd6deea3174d52ceeb770c3ccb40fa7af22b1edc0f51c2f29018 0.600000000000 1516788 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": 1046979, "vin": [ { "gen": { "height": 1046969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a2feafa60e8fd6deea3174d52ceeb770c3ccb40fa7af22b1edc0f51c2f29018" } } ], "extra": [ 1, 41, 133, 191, 102, 8, 167, 35, 90, 232, 131, 116, 4, 139, 109, 135, 197, 74, 107, 71, 233, 196, 10, 131, 50, 242, 146, 174, 237, 164, 167, 37, 37, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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