Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14da215b0353312b73f2ac2e53b2bb5aaea83ed31b9e8b4334631617050ce15d

Tx prefix hash: 690ad35e44d4ba4c34130589f755bf20cf83e2c4757e35171b27d772a89c4da4
Tx public key: 775cb98e19f1d3e50ddd8ccc0124fe24a9feca1bb4715a49a0d5751571be438a
Timestamp: 1717640493 Timestamp [UCT]: 2024-06-06 02:21:33 Age [y:d:h:m:s]: 01:158:05:49:18
Block: 1037984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371681 RingCT/type: yes/0
Extra: 01775cb98e19f1d3e50ddd8ccc0124fe24a9feca1bb4715a49a0d5751571be438a021100000002d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67332821114060f0d1a5d3684b5f4b9cc317f6ea5756b1b32db9d089615812aa 0.600000000000 1506543 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": 1037994, "vin": [ { "gen": { "height": 1037984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67332821114060f0d1a5d3684b5f4b9cc317f6ea5756b1b32db9d089615812aa" } } ], "extra": [ 1, 119, 92, 185, 142, 25, 241, 211, 229, 13, 221, 140, 204, 1, 36, 254, 36, 169, 254, 202, 27, 180, 113, 90, 73, 160, 213, 117, 21, 113, 190, 67, 138, 2, 17, 0, 0, 0, 2, 215, 73, 245, 17, 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