Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e958804045d84e874d7f1bb50f1373378d05975acbee646112607fd0d1624077

Tx prefix hash: ae83ed11e09a06f4ec199cf46b5f3d756bc8a8f3d561598e2067f0db3abc3e6c
Tx public key: c8ed0c7cb643509df864a9be04335c813e7146dff186be6a1c7bd50b1297c3b9
Timestamp: 1728383321 Timestamp [UCT]: 2024-10-08 10:28:41 Age [y:d:h:m:s]: 00:206:00:57:03
Block: 1127057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147065 RingCT/type: yes/0
Extra: 01c8ed0c7cb643509df864a9be04335c813e7146dff186be6a1c7bd50b1297c3b9021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d1bcc4e05f9347e360c0ca4ee7e64f34a2cb5c719f6e52b728faad78c997cb9 0.600000000000 1609856 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": 1127067, "vin": [ { "gen": { "height": 1127057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d1bcc4e05f9347e360c0ca4ee7e64f34a2cb5c719f6e52b728faad78c997cb9" } } ], "extra": [ 1, 200, 237, 12, 124, 182, 67, 80, 157, 248, 100, 169, 190, 4, 51, 92, 129, 62, 113, 70, 223, 241, 134, 190, 106, 28, 123, 213, 11, 18, 151, 195, 185, 2, 17, 0, 0, 0, 7, 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