Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10f5a30c2bfc22ddbb1f5d7f8adc3385d7a408bc2ff5544f8ae5902f67c33d67

Tx prefix hash: c54adfeabf3fa677e03d87d408752df61abad52701a9fad1a55e157da02f2a95
Tx public key: 0b1aa03da3ad19f4eabc1967e312a1852b41849ed9745169d2cb9c83d75fc9c1
Timestamp: 1731139328 Timestamp [UCT]: 2024-11-09 08:02:08 Age [y:d:h:m:s]: 00:170:06:46:17
Block: 1149824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121549 RingCT/type: yes/0
Extra: 010b1aa03da3ad19f4eabc1967e312a1852b41849ed9745169d2cb9c83d75fc9c10211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 022a4f9be5b3b50229012ea420b5954df65e4697f96af08b39707697e6c95a72 0.600000000000 1634991 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": 1149834, "vin": [ { "gen": { "height": 1149824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "022a4f9be5b3b50229012ea420b5954df65e4697f96af08b39707697e6c95a72" } } ], "extra": [ 1, 11, 26, 160, 61, 163, 173, 25, 244, 234, 188, 25, 103, 227, 18, 161, 133, 43, 65, 132, 158, 217, 116, 81, 105, 210, 203, 156, 131, 215, 95, 201, 193, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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