Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06e94043b3b155a75f489fdcbb407b85c9e42e6d1f5485ed9308d32969bcfc5b

Tx prefix hash: 789be2ad81f63e73591063a18ad2c7f77c48fbf050a93f6dd3066ade127da540
Tx public key: 836520121a77ca2ca33461e4e45e8f52b4c3cc14f05e9c3789e8e4bc2396a9df
Timestamp: 1719168216 Timestamp [UCT]: 2024-06-23 18:43:36 Age [y:d:h:m:s]: 00:243:17:17:32
Block: 1050641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174123 RingCT/type: yes/0
Extra: 01836520121a77ca2ca33461e4e45e8f52b4c3cc14f05e9c3789e8e4bc2396a9df02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7daca3406646b50da156e4c5caa97c12cf12301d045092a5edf7e9dbd98d422c 0.600000000000 1520816 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": 1050651, "vin": [ { "gen": { "height": 1050641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7daca3406646b50da156e4c5caa97c12cf12301d045092a5edf7e9dbd98d422c" } } ], "extra": [ 1, 131, 101, 32, 18, 26, 119, 202, 44, 163, 52, 97, 228, 228, 94, 143, 82, 180, 195, 204, 20, 240, 94, 156, 55, 137, 232, 228, 188, 35, 150, 169, 223, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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