Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc4e94505b9f66722afa315d48dfb7700f447388003bfea1cc4515f905109a1f

Tx prefix hash: d89d9a4ea5a78dea6d7816753ed7eecdae37315786ad1430b9e9a564fcffc5d7
Tx public key: f30e6b7ed89124361bb5d2aaa8d45e6775f56391f13c5b81fb10fe4c165bbcf9
Timestamp: 1726671967 Timestamp [UCT]: 2024-09-18 15:06:07 Age [y:d:h:m:s]: 00:113:13:25:02
Block: 1112861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81206 RingCT/type: yes/0
Extra: 01f30e6b7ed89124361bb5d2aaa8d45e6775f56391f13c5b81fb10fe4c165bbcf9021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e498b3ff8522ef16e000df4bf082d47c1022d5ce6bbeaec55f3f074fae26986 0.600000000000 1592334 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": 1112871, "vin": [ { "gen": { "height": 1112861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e498b3ff8522ef16e000df4bf082d47c1022d5ce6bbeaec55f3f074fae26986" } } ], "extra": [ 1, 243, 14, 107, 126, 216, 145, 36, 54, 27, 181, 210, 170, 168, 212, 94, 103, 117, 245, 99, 145, 241, 60, 91, 129, 251, 16, 254, 76, 22, 91, 188, 249, 2, 17, 0, 0, 0, 3, 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