Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2815d46edabda8c4004aab3fa0f13d1ee8f03adb7f5acd8efba6395504ff1de

Tx prefix hash: 05c4736c62e7ae66ff50e56bbd0968f12a2252a9bf74aa70d10522eb1e6cc03c
Tx public key: e4194463b36d81a9bca09c78b5e93aa360c2026203ea5a1cf955a926d4d7c51e
Timestamp: 1724776254 Timestamp [UCT]: 2024-08-27 16:30:54 Age [y:d:h:m:s]: 00:231:06:42:08
Block: 1097143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165169 RingCT/type: yes/0
Extra: 01e4194463b36d81a9bca09c78b5e93aa360c2026203ea5a1cf955a926d4d7c51e021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84345352a6eb0bc79f7362560e5f3630e8002f9f234070be0ff48951e81e4988 0.600000000000 1572458 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": 1097153, "vin": [ { "gen": { "height": 1097143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84345352a6eb0bc79f7362560e5f3630e8002f9f234070be0ff48951e81e4988" } } ], "extra": [ 1, 228, 25, 68, 99, 179, 109, 129, 169, 188, 160, 156, 120, 181, 233, 58, 163, 96, 194, 2, 98, 3, 234, 90, 28, 249, 85, 169, 38, 212, 215, 197, 30, 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