Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e12525acdb6c72c48cad0f5634f8d1b4e657c2dda004413149eb8628bb0c876

Tx prefix hash: d8d74fd44ac56c8c8443b4bedd97e6825a0219050f50ff53715ab44951cb0969
Tx public key: 65cb4f629caaa44190cf287999e8eac9cb0de6eb9eb5ad3a1c2138f1276f9555
Timestamp: 1743329622 Timestamp [UCT]: 2025-03-30 10:13:42 Age [y:d:h:m:s]: 00:286:07:57:42
Block: 1250480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202464 RingCT/type: yes/0
Extra: 0165cb4f629caaa44190cf287999e8eac9cb0de6eb9eb5ad3a1c2138f1276f95550211000000019ba629df000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0921831daf19ac9863e602bb2c124d32dc2514f931dc882e0e499fb8b41b0031 0.600000000000 1737529 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": 1250490, "vin": [ { "gen": { "height": 1250480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0921831daf19ac9863e602bb2c124d32dc2514f931dc882e0e499fb8b41b0031" } } ], "extra": [ 1, 101, 203, 79, 98, 156, 170, 164, 65, 144, 207, 40, 121, 153, 232, 234, 201, 203, 13, 230, 235, 158, 181, 173, 58, 28, 33, 56, 241, 39, 111, 149, 85, 2, 17, 0, 0, 0, 1, 155, 166, 41, 223, 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